remove the feature the packstack have been own is not good idea, and would affect many user.

On Thu, Jun 26, 2014 at 8:55 PM, Stefan Apostoaie <stefan.apostoaie(a)softvision.ro <mailto:stefan.apostoaie@softvision.ro>> wrote: Hello, I was working on integrating a neutron plugin in Packstack and successfully done so for the Packstack havana. I then tried porting the changes into Packstack for icehouse and noticed some changes that limit my options: 1. We need to run the metadata agents on all the compute nodes so we previously used the CONFIG_NEUTRON_METADATA_HOSTS option to specify this. In the latest version this was deprecated and replaced by CONFIG_NETWORK_HOSTS so the metadata agent will only be installed on the network node. 2. The CONFIG_CONTROLLER_HOST replaces several other options including CONFIG_HORIZON_HOST. In our setup we need to run horizon on the public network and the other services on the private network. The missing CONFIG_HORIZON_HOST means that the dashboard will only be available on our private network and we need to manually update the horizon and httpd config files. 3. The CONFIG_NOVA_VNCPROXY_HOST was also replaced by CONFIG_CONTROLLER_HOST so the VM console doesn't work outside our private network. 4. An issue that I've encountered when running packstack was a mysql puppet error "service mysqld start failed: my_default_config doesn't take the --mysqld parameter". The mysqld service started when I tried from the command line and after that Packstack worked. Not sure it's related to Packstack or some mysql server issue on our machines. The servers we use have CentOS 6.5 installed. I know that having only three types of hosts (CONTROLLER, NETWORK, and COMPUTE) simplifies things when installing basic Openstack configurations (with the ml2, linux bridge, or ovs plugin), but for us it becomes a lot more complicated to make Packstack do what we need. I believe that these changes affect Packstacks' flexibility. Now we cannot install horizon, cinder, swift, or keystone on a different host because they are tied to the CONFIG_CONTROLLER_HOST option. Is there a way to override the CONFIG_CONTROLLER_HOST, CONFIG_NETWORK_HOSTS, and CONFIG_COMPUTE_HOSTS? Can packstack havana be used to install Openstack icehouse by configuring yum to use the icehouse rdo repository? Regards, Stefan A

On 26.6.2014 15:33, Perry Myers wrote: > On 06/26/2014 09:23 AM, Shake Chen wrote: >> remove the feature the packstack have been own is not good idea, and >> would affect many user. > > Part of the reason for the reduction in scope of Packstack is due to > resource constraints for the team that is working on Packstack, Puppet > and Foreman. > > If we could get some folks outside of Red Hat to become upstream > contributors and more importantly maintainers of Packstack, then that > would alleviate some of the scope creep concerns and perhaps Packstack > could be expanded a bit. > > But right now with the majority of the effort solely coming from a > handful of Red Hatters, we just don't have the bandwidth and hence the > scope of Packstack was reduced to be purely an all-in-one/demo tool. Well, it was created as a proof-of-concept/demo tool in the first place. If you want sophisticated multi-node installer, packstack isn't the right tool for that job.

Cheers Jakub _______________________________________________ Rdo-list mailing list Rdo-list(a)redhat.com https://www.redhat.com/mailman/listinfo/rdo-list

Foreman is the right tool! ;) Red Hat has great docs about it: https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Lin... Regards --- JuanFra Rodriguez Cardoso 2014-06-26 16:52 GMT+02:00 Madko <madko77(a)gmail.com&gt;: > > > 2014-06-26 16:44 GMT+02:00 Jakub Ruzicka <jruzicka(a)redhat.com&gt;: > > On 26.6.2014 15:33, Perry Myers wrote: >> > On 06/26/2014 09:23 AM, Shake Chen wrote: >> >> remove the feature the packstack have been own is not good idea, and >> >> would affect many user. >> > >> > Part of the reason for the reduction in scope of Packstack is due to >> > resource constraints for the team that is working on Packstack, Puppet >> > and Foreman. >> > >> > If we could get some folks outside of Red Hat to become upstream >> > contributors and more importantly maintainers of Packstack, then that >> > would alleviate some of the scope creep concerns and perhaps Packstack >> > could be expanded a bit. >> > >> > But right now with the majority of the effort solely coming from a >> > handful of Red Hatters, we just don't have the bandwidth and hence the >> > scope of Packstack was reduced to be purely an all-in-one/demo tool. >> >> Well, it was created as a proof-of-concept/demo tool in the first place. >> >> If you want sophisticated multi-node installer, packstack isn't the >> right tool for that job. >> >> > Good to know, what is the right tool for that job? I mean multi-node > installer. > > >> Cheers >> Jakub >> >> >> >> _______________________________________________ >> Rdo-list mailing list >> Rdo-list(a)redhat.com >> https://www.redhat.com/mailman/listinfo/rdo-list >> > > > Best regards, > -- > Edouard Bourguignon > > _______________________________________________ > Rdo-list mailing list > Rdo-list(a)redhat.com > https://www.redhat.com/mailman/listinfo/rdo-list > >

btw, the lastest reference should be this one? https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Lin... On Thu, Jun 26, 2014 at 11:09 PM, Madko <madko77(a)gmail.com&gt; wrote: > Thanks, I will give it a try. I hope with more luck than packstack. > > > 2014-06-26 16:59 GMT+02:00 JuanFra Rodriguez Cardoso > <juanfra.rodriguez.cardoso(a)gmail.com&gt;: > >> Foreman is the right tool! ;) >> Red Hat has great docs about it: >> https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Lin... >> >> Regards >> --- >> JuanFra Rodriguez Cardoso >> >> >> 2014-06-26 16:52 GMT+02:00 Madko <madko77(a)gmail.com&gt;: >> >>> >>> >>> >>> 2014-06-26 16:44 GMT+02:00 Jakub Ruzicka <jruzicka(a)redhat.com&gt;: >>> >>>> On 26.6.2014 15:33, Perry Myers wrote: >>>> > On 06/26/2014 09:23 AM, Shake Chen wrote: >>>> >> remove the feature the packstack have been own is not good idea, and >>>> >> would affect many user. >>>> > >>>> > Part of the reason for the reduction in scope of Packstack is due to >>>> > resource constraints for the team that is working on Packstack, Puppet >>>> > and Foreman. >>>> > >>>> > If we could get some folks outside of Red Hat to become upstream >>>> > contributors and more importantly maintainers of Packstack, then that >>>> > would alleviate some of the scope creep concerns and perhaps Packstack >>>> > could be expanded a bit. >>>> > >>>> > But right now with the majority of the effort solely coming from a >>>> > handful of Red Hatters, we just don't have the bandwidth and hence the >>>> > scope of Packstack was reduced to be purely an all-in-one/demo tool. >>>> >>>> Well, it was created as a proof-of-concept/demo tool in the first place. >>>> >>>> If you want sophisticated multi-node installer, packstack isn't the >>>> right tool for that job. >>>> >>> >>> Good to know, what is the right tool for that job? I mean multi-node >>> installer. >>> >>>> >>>> Cheers >>>> Jakub >>>> >>>> >>>> >>>> _______________________________________________ >>>> Rdo-list mailing list >>>> Rdo-list(a)redhat.com >>>> https://www.redhat.com/mailman/listinfo/rdo-list >>> >>> >>> >>> Best regards, >>> -- >>> Edouard Bourguignon >>> >>> _______________________________________________ >>> Rdo-list mailing list >>> Rdo-list(a)redhat.com >>> https://www.redhat.com/mailman/listinfo/rdo-list >>> >> > > > > -- > Edouard Bourguignon > > _______________________________________________ > Rdo-list mailing list > Rdo-list(a)redhat.com > https://www.redhat.com/mailman/listinfo/rdo-list >

Have you installed centos-SCL repo? Regards, --- JuanFra Rodriguez Cardoso 2014-06-27 9:30 GMT+02:00 Madko <madko77(a)gmail.com&gt;: No more luck :( > I can't even install foreman due to this bug => > https://bugzilla.redhat.com/show_bug.cgi?id=1091564 > any idea how to make it work? > > > 2014-06-26 18:03 GMT+02:00 Kun Huang <gareth(a)openstacker.org&gt;: > >> btw, the lastest reference should be this one? >> >> >> https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Lin... >> >> On Thu, Jun 26, 2014 at 11:09 PM, Madko <madko77(a)gmail.com&gt; wrote: >> > Thanks, I will give it a try. I hope with more luck than packstack. >> > >> > >> > 2014-06-26 16:59 GMT+02:00 JuanFra Rodriguez Cardoso >> > <juanfra.rodriguez.cardoso(a)gmail.com&gt;: >> > >> >> Foreman is the right tool! ;) >> >> Red Hat has great docs about it: >> >> >> https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Lin... >> >> >> >> Regards >> >> --- >> >> JuanFra Rodriguez Cardoso >> >> >> >> >> >> 2014-06-26 16:52 GMT+02:00 Madko <madko77(a)gmail.com&gt;: >> >> >> >>> >> >>> >> >>> >> >>> 2014-06-26 16:44 GMT+02:00 Jakub Ruzicka <jruzicka(a)redhat.com&gt;: >> >>> >> >>>> On 26.6.2014 15:33, Perry Myers wrote: >> >>>> > On 06/26/2014 09:23 AM, Shake Chen wrote: >> >>>> >> remove the feature the packstack have been own is not good idea, >> and >> >>>> >> would affect many user. >> >>>> > >> >>>> > Part of the reason for the reduction in scope of Packstack is due >> to >> >>>> > resource constraints for the team that is working on Packstack, >> Puppet >> >>>> > and Foreman. >> >>>> > >> >>>> > If we could get some folks outside of Red Hat to become upstream >> >>>> > contributors and more importantly maintainers of Packstack, then >> that >> >>>> > would alleviate some of the scope creep concerns and perhaps >> Packstack >> >>>> > could be expanded a bit. >> >>>> > >> >>>> > But right now with the majority of the effort solely coming from a >> >>>> > handful of Red Hatters, we just don't have the bandwidth and >> hence the >> >>>> > scope of Packstack was reduced to be purely an all-in-one/demo >> tool. >> >>>> >> >>>> Well, it was created as a proof-of-concept/demo tool in the first >> place. >> >>>> >> >>>> If you want sophisticated multi-node installer, packstack isn't the >> >>>> right tool for that job. >> >>>> >> >>> >> >>> Good to know, what is the right tool for that job? I mean multi-node >> >>> installer. >> >>> >> >>>> >> >>>> Cheers >> >>>> Jakub >> >>>> >> >>>> >> >>>> >> >>>> _______________________________________________ >> >>>> Rdo-list mailing list >> >>>> Rdo-list(a)redhat.com >> >>>> https://www.redhat.com/mailman/listinfo/rdo-list >> >>> >> >>> >> >>> >> >>> Best regards, >> >>> -- >> >>> Edouard Bourguignon >> >>> >> >>> _______________________________________________ >> >>> Rdo-list mailing list >> >>> Rdo-list(a)redhat.com >> >>> https://www.redhat.com/mailman/listinfo/rdo-list >> >>> >> >> >> > >> > >> > >> > -- >> > Edouard Bourguignon >> > >> > _______________________________________________ >> > Rdo-list mailing list >> > Rdo-list(a)redhat.com >> > https://www.redhat.com/mailman/listinfo/rdo-list >> > >> > > > > -- > Edouard Bourguignon >