设为首页 收藏本站
查看: 1030|回复: 0

[经验分享] Going Native with OpenStack Centric Applications: Overview

[复制链接]
累计签到:6 天
连续签到:1 天
发表于 2015-10-11 10:58:13 | 显示全部楼层 |阅读模式
  Cloud infrastructure is useless without applications running atop, providing business servi DSC0000.png cesand solving customer needs. So, as applications ascend to the throne as the rightful king of cloud, focus sharpens on their support within OpenStack-based clouds. With this focus, let’s walk through a survey of components and projects supporting applicationsin OpenStack, understanding what a day in the life of an application in OpenStack is like. We’ll start with an overview of the application ecosystem comprised of a number of supporting projects. In the ecosystem overview below, relevant OpenStack projectsare presented in context of existing, similar technologies with which you may be familiar. These similar technologies both under and overlap functionality of the respective OpenStack project, but are shown to hasten your general understanding of which bucketthese projects fall into by way of tech you may already know (so, add a pinch of salt when considering relevancy of suggested affiliated technologies).
Application Ecosystem by Project
  Like individual lines in a product family, projects within OpenStack engulf and extend one another for related, but distinct purposes and target use cases. OpenStack developers are cautious to apply DRY principles in their approach to project design, integratingfunctionality rather than reinventing the wheel as they go. The ProjectFocus and Relationship diagram both figuratively and literally places project relationships into round bubbles, identifying conceptual starting points for the genesis of an application as well as the reuse of some projects by others.

  • ApplicationBlueprint Designer – Merlin

    • RavelloSystems, UrbanCode, CliQr, Prime Service Catalog*…

  • ApplicationLifecycle Management PaaS – Solum

    • Similar technologies (ALM) – Atlassian Suite, HP ALM, Cloudpipes, Serena…
    • Similar technologies (PaaS) – Openshift, Cloud Foundry, BlueMix, AppScale, Heroku, App Engine…

    DSC0001.png Project Focus and Relationship
  • ApplicationCatalog – Murano

    • Similar technologies – AppStack, CliQr, ITApp, AppDirect…

  • ApplicationStack Provisioning –Heat, Magnum

    • Similar technologies – AWS Elastic Beanstalk, Kubernetes, GearD, Warden, Fleet, MaestroNG, CliQr, Nirmata…

  • ApplicationContainers – Docker

    • Similar technologies – OpenVZ, Linux V-Server, FreeBSD jails, AIX Workload Partitions and Solaris Containers

  • ApplicationConfiguration Management – Puppet, Chef

    • Similar technologies – Heat, Salt, Ansible, Satori*…

A Day in the Life of an OpenStack-Native Application
  The ApplicationLifecycle Flows diagram defines different entrance points by which applications are birthed and the flow between different OpenStack projects within their lifecycle.
Application Lifecycle Flows
  Users may design applicationswith Merlin, develop applicationswith Solum, orderapplicationswith Murano, deploy applicationsand resources with Heat and manage applicationswith Puppet/other configuration managers.
“Applications”
  Given that applications are varied in nature both in terms of their type and complexity, let’s take a moment to review their possible shapes and sizes. With regard to types of applications, some are  image-based and some are container-based while othersare offered simply as a SaaS subscription (implying that a singular instance of this application may serve multiple tenants). Applications may be cloud-native (designed to be scaled out, highly distributed, service-oriented) or enterprise-architected (designedto be scaled up, designed with layers and functional domains). Application complexity ranges from single component (image or container) to multiple component, multiple environment, multiple OpenStack deployments to OpenStack and other systems. Applicationsmay be comprised of multiple components (e.g. MySQL, PHP, Apache) or a singular components (MySQL). Application components may be distributed or contained within a given container, VM or cloud. With these possibilities in mind, let’s begin our survey of theirsupport with the OpenStack-native application catalog – Murano in the next post in this series.
  
  
  from: http://blog.gingergeek.com/2014/11/going-native-with-openstack-centric-applications-overview/
  
GoingNative with OpenStack Centric Applications: Murano http://blog.gingergeek.com/2014/11/going-native-with-openstack-centric-applications-murano/?utm_campaign=899&utm_medium=twitter&utm_source=twitter&utm_campaign=OpenStack+Now&utm_source=hs_email&utm_medium=email&utm_content=15033090&_hsenc=p2ANqtz-8btYZqIYYHnVdCDvMG1XFFZA1uQnkdJmZKYUtuqZMJCNrLN8EWrIinmMuxLoo6xWQlylXIqsX3Z68PpSy_BL1HCCNzCQ&_hsmi=15033090

运维网声明 1、欢迎大家加入本站运维交流群:群②:261659950 群⑤:202807635 群⑦870801961 群⑧679858003
2、本站所有主题由该帖子作者发表,该帖子作者与运维网享有帖子相关版权
3、所有作品的著作权均归原作者享有,请您和我们一样尊重他人的著作权等合法权益。如果您对作品感到满意,请购买正版
4、禁止制作、复制、发布和传播具有反动、淫秽、色情、暴力、凶杀等内容的信息,一经发现立即删除。若您因此触犯法律,一切后果自负,我们对此不承担任何责任
5、所有资源均系网友上传或者通过网络收集,我们仅提供一个展示、介绍、观摩学习的平台,我们不对其内容的准确性、可靠性、正当性、安全性、合法性等负责,亦不承担任何法律责任
6、所有作品仅供您个人学习、研究或欣赏,不得用于商业或者其他用途,否则,一切后果均由您自己承担,我们对此不承担任何法律责任
7、如涉及侵犯版权等问题,请您及时通知我们,我们将立即采取措施予以解决
8、联系人Email:admin@iyunv.com 网址:www.yunweiku.com

所有资源均系网友上传或者通过网络收集,我们仅提供一个展示、介绍、观摩学习的平台,我们不对其承担任何法律责任,如涉及侵犯版权等问题,请您及时通知我们,我们将立即处理,联系人Email:kefu@iyunv.com,QQ:1061981298 本贴地址:https://www.yunweiku.com/thread-125365-1-1.html 上篇帖子: openstack cinder default volume 下篇帖子: 谁在掌管着OpenStack项目
您需要登录后才可以回帖 登录 | 立即注册

本版积分规则

扫码加入运维网微信交流群X

扫码加入运维网微信交流群

扫描二维码加入运维网微信交流群,最新一手资源尽在官方微信交流群!快快加入我们吧...

扫描微信二维码查看详情

客服E-mail:kefu@iyunv.com 客服QQ:1061981298


QQ群⑦:运维网交流群⑦ QQ群⑧:运维网交流群⑧ k8s群:运维网kubernetes交流群


提醒:禁止发布任何违反国家法律、法规的言论与图片等内容;本站内容均来自个人观点与网络等信息,非本站认同之观点.


本站大部分资源是网友从网上搜集分享而来,其版权均归原作者及其网站所有,我们尊重他人的合法权益,如有内容侵犯您的合法权益,请及时与我们联系进行核实删除!



合作伙伴: 青云cloud

快速回复 返回顶部 返回列表