Re: [openstack-dev] [Fuel] update existing plugin and add new ones
There was a discussion on whether to put all the fuel plugins into the single repository or have them separate. The problems with all the fuel plugins in single repository are following: - it is impossible to make a branch on a single plugin, branch is applied to the whole repository and all the plugins - plugins may have different release cycles, we will get lots of unnecessary merges/rebases - rebasing can be a pain. If I have a branch, I have to rebase when some other plugins change - there should be someone who manage merging to master, the person who "owns" all the plugins Having all the plugins in single repository will cause interference. if I do some plugin, I have to consider what developers of other plugins do. Anton On Tue, Jan 6, 2015 at 7:00 PM, wrote: > Hello, > > > > Actually there is two different fuel plugins git repositories. One in > stackforge and the other in mirantis: > > https://github.com/stackforge/fuel-plugins > > https://github.com/Mirantis/fuel-plugins > > > > it is a little bit confusing. Why needing two different repositories? > > > > which one should be used in order to: > > -add new plugin > > -update/correct exisiting one (for example adding 7-mode and e-series > support to cinder netapp plugin according to > https://bugs.launchpad.net/fuel/+bug/1405186) > > How are going to be manage version? There is a stable/6.0 branch from > stackforge repo but not mirantis one > > > > Regards, > > > > Samuel Bartel > > Orange > > > > > > > > _ > > Ce message et ses pieces jointes peuvent contenir des informations > confidentielles ou privilegiees et ne doivent donc > pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu > ce message par erreur, veuillez le signaler > a l'expediteur et le detruire ainsi que les pieces jointes. Les messages > electroniques etant susceptibles d'alteration, > Orange decline toute responsabilite si ce message a ete altere, deforme ou > falsifie. Merci. > > This message and its attachments may contain confidential or privileged > information that may be protected by law; > they should not be distributed, used or copied without authorisation. > If you have received this email in error, please notify the sender and delete > this message and its attachments. > As emails may be altered, Orange is not liable for messages that have been > modified, changed or falsified. > Thank you. > > > ___ > OpenStack-dev mailing list > OpenStack-dev@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > __ 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
Re: [openstack-dev] [Fuel] update existing plugin and add new ones
Ah, bad paste, sorry. All the details around developing and certifying a plug-in can be found here: http://docs.mirantis.com/openstack/fuel/fuel-6.0/plugin-dev.html -Christopher ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Fuel] update existing plugin and add new ones
On Tue, Jan 6, 2015 at 7:00 AM, wrote: > Actually there is two different fuel plugins git repositories. One in > stackforge and the other in mirantis: > > https://github.com/stackforge/fuel-plugins Stackforge plug-ins - used for plug-ins developed by Fuel Core team. > https://github.com/Mirantis/fuel-plugins Mirantis plug-ins - used for plug-ins developed by Partner Integrations and MOS teams. > it is a little bit confusing. Why needing two different repositories? Samuel, I agree, it is confusing. From what I see the repo on stackforge is the one that matters from the perspective of someone building a new plugin. For those just looking to download and use a plug-in, the directory of certified and non-certified plug-ins for Fuel will live here: https://software.mirantis.com/download-mirantis-openstack-fuel-plug-ins/ All the details around developing and certifying a plug-in can be found here: https://software.mirantis.com/download-mirantis-openstack-fuel-plug-ins/ Feedback on improving the docs is greatly appreciated! > How are going to be manage version? There is a stable/6.0 branch from > stackforge repo but not mirantis one Since plugins are developed and built outside Fuel, the plugins have their own versions (see metadata.yaml file). I expect we will make things a little clearer in the weeks to come, but please share your feedback and thoughts on how to make this work better. Thanks! -Christopher ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [Fuel] update existing plugin and add new ones
Hello, Actually there is two different fuel plugins git repositories. One in stackforge and the other in mirantis: https://github.com/stackforge/fuel-plugins https://github.com/Mirantis/fuel-plugins it is a little bit confusing. Why needing two different repositories? which one should be used in order to: -add new plugin -update/correct exisiting one (for example adding 7-mode and e-series support to cinder netapp plugin according to https://bugs.launchpad.net/fuel/+bug/1405186) How are going to be manage version? There is a stable/6.0 branch from stackforge repo but not mirantis one Regards, Samuel Bartel Orange _ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you. ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
