Open Stack

Hi Lance,

The Enterprise WG meet Tuesday weekly at 11am (Pacific timezone)
https://wiki.openstack.org/wiki/Enterprise_Working_Group

Great to see your interest on this Workload Reference Architecture!

Stay tuned for further update on this matter.

Thanks!
Leong.


From: Lance Haig [mailto:lnhaig at gmail.com]
Sent: Friday, December 2, 2016 1:00 AM
To: enterprise-wg at lists.openstack.org
Subject: Re: [Enterprise] EWG Workload Reference Architecture - Git Repo


Hi,



I just found out about this list.

I am currently working on heat code for architecture of applications for corporates within my company.

is there an IRC or similar channel for this wg?

I would like to contribute

Regards

Lance



In the last Enterprise WG meeting, I proposed to move the development of workload reference architecture into OpenStack github and review system/process.

Most agreed and support this approach. I just want to bring this up to this maillist in case of anyone who missed the last meeting.



As most are aware, in the previous Newton cycle, we have published two Workload Reference Architecture (Web Application & Big Data) which are now available at https://www.openstack.org/software/sample-configs. (eCommerce is in the final stage of publication).



With this, we can:



1.       Create a more scalable process for on-going enhancement/development/creation of existing or new workload reference architecture (e.g. container, media transcoding, enterprise database, PaaS, etc).



2.       Reach out to wider community and encourage more people to contribute.



3.       Mitigate EWG resources bottleneck on developing workload reference architecture.



4.       Allow parallel development of multiple reference architectures at any release cycle.



5.       Embrace OpenStack 4 Open principles.



To achieve this, few things needs to be done:



1.       Create a github repo to host EWG Workload Reference Architecture. (I have submitted the github request)



2.       Develop a common template or format for the content writing. (pending)



3.       Decide a directory structure for hosting each individual workload reference architecture (documents, diagram, sample code such as heat or murano), potentially with multiple "version" or "release". (pending)



4.       Form initial team of core-reviewer for this repo to validate/approve content. (pending)



Let me know if you have any questions.

Thanks!



Regards,

---

Yih Leong Sun, PhD

Senior Software Cloud Architect | Open Source Technology Center | Intel Corporation

yih.leong.sun at intel.com<http://lists.openstack.org/cgi-bin/mailman/listinfo/enterprise-wg><mailto:yih.leong.sun at intel.com<http://lists.openstack.org/cgi-bin/mailman/listinfo/enterprise-wg>> | +1 503 264 0610
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/enterprise-wg/attachments/20161202/e11deb1b/attachment.html>