On 11/19/2015 09:32 AM, Kevin Carter wrote: > I don't believe we should have a class system in the OS's that we choose > to support. If we're going to bring in a new OS I think we should first > bring it in using non-voting jobs however once all of the bits have been > finalized the supported OS should be able to pass the same sets of tests > as everything else. Now, we may run into various applications that may > not be compatible or available on different distros, which is fine, but > in that case we should call out the deficiencies marking a specific job > as non-voting until we can see about resolving the issues. I would like > to avoid creating second class operating systems within OSA if at all > possible. > > -- > > Kevin Carter > IRC: cloudnull > > On 11/19/2015 09:21 AM, Major Hayden wrote: >> On 11/18/2015 04:19 AM, Jesse Pretorius wrote: >>> The current community has done some research into appropriate patterns to >>> use and has a general idea of how to do it - but in order to actually >>> execute there need to be enough people who commit to actually maintaining >>> the work once it's done. We don't want to carry the extra code if we don't >>> also pick up extra contributors to maintain the code. >> >> Should there be a concept of primary and secondary operating systems >> supported by openstack-ansible? I'm thinking something similar to the tiers >> of hypervisors in OpenStack where some are tested heavily with gating while >> others have a lighter amount of testing. >> >> We might be able to have something along the lines of: >> >> * Primary OS: Used in gate checks, heavily tested >> * Secondary OS: Not used in gate checks, lightly tested >> * Tertiary OS: Support in WIP state, not tested >> >> -- >> Major Hayden >> >> _______________________________________________ >> OpenStack-operators mailing list >> openstack-operat...@lists.openstack.org >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators >> > > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >
I would like this to be the option we go with. I've wanted to add another OS to OSA but need to fulfil other prerequisites (adding the OS to disk-image-builder) but once I do I'll be working on adding support for it, have some vacation coming up... -- -- Matthew Thode (prometheanfire) __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
