- openstack-discuss - lists.openstack.org

[publiccloud]Choice of deployment tools
by Cody 19 Dec '18

19 Dec '18

Hello stackers, What deployment tools would be of your choice for deploying a public IaaS with an initial size of 200~300 nodes? Would TripleO be suitable for this cluster size? Thank you very much. Wish you all a happy holiday season! Best regards, Cody

5 7

[neutron][qos] IRC meeting Jan 1, 2019
by Rodolfo Alonso 19 Dec '18

19 Dec '18

Hello: Next meeting on January 1, 2019, is canceled. The next meeting of the Neutron QoS subteam will be on January 15, 2019. Regards.

1 0

Denver Open Infrastructure Summit CFP Open
by Ashlee Ferguson 19 Dec '18

19 Dec '18

Hi everyone, The OpenStack Summit has a new name! To reflect our evolving community, the first Open Infrastructure Summit <https://www.openstack.org/summit/denver-2019/> will be held in Denver, Colorado April 29 - May 1, 2019. The Call for Presentations (CFP) is now open, and the deadline to submit your presentations, panels, and workshops <https://www.openstack.org/summit/denver-2019/call-for-presentations> is Wednesday, January 23 at 11:59pm PT (January 24 at 7:59am UTC). Here are the Summit Tracks <https://www.openstack.org/summit/denver-2019/summit-categories> as well as the Programming Committee nomination form <https://openstackfoundation.formstack.com/forms/openstackdenver2019_program…> if you are interested in helping shape the content of the Summit. The content submission process for the Forum and Project Teams Gathering will be managed separately in the upcoming months. SUBMIT YOUR PRESENTATION <https://www.openstack.org/summit/denver-2019/call-for-presentations> New for the Denver Summit: Based on previous track chair and attendee feedback, we have added / updated three Tracks: Security, Getting Started, Open Development. You can find the Track descriptions here <https://www.openstack.org/summit/denver-2019/summit-categories>. In addition to OpenStack, you’ll see the OSF pilot projects —Airship, Kata Containers, StarlingX and Zuul —front and center alongside Ansible, Cloud Foundry, Docker, Kubernetes, and many more. The Open Infrastructure Summit, has evolved to recognize our diverse audience, and to signal to the market that the event is relevant for all IT infrastructure decision makers. We are working with the Programming Committee members to share the topics they’re looking for within each Track. Stay tuned on Superuser as we post these recommendations. If you’re interested in influencing the Summit content, apply to be a Programming Committee member <https://openstackfoundation.formstack.com/forms/openstackdenver2019_program…>*, where you can also find a full list of time requirements and expectations. Nominations will close on January 4, 2019. *OSF Staff will serve as the Programming Committee for the Getting Started Track. Denver Summit registration and sponsor sales are currently open. Learn more <https://www.openstack.org/summit/denver-2019> Please email speakersupport(a)openstack.org <mailto:speakersupport@openstack.org> with any questions or feedback. Cheers, Ashlee Ashlee Ferguson OpenStack Foundation ashlee(a)openstack.org

1 0

Firefox context search text across openstack related websites like codesearch, logstash, launchpad
by Sorin Sbarnea 19 Dec '18

19 Dec '18

As many of us have to search for pieces of text on many places, like codesearch, logstash,.... I invested some time in making this possible with a right-click. Warning: requires Firefox extension. Details https://github.com/openstack/coats#context-search-for-firefox <https://github.com/openstack/coats#context-search-for-firefox> I hope it would make your life easier. PS. Improvements on the search engines definition files are welcomed, on Gerrit :) Cheers, Sorin Sbarnea

1 0

[TripleO] flattening tripleo-heat-templates: what about pacemaker?
by Cédric Jeanneret 18 Dec '18

18 Dec '18

Hello folks, While working on the service flattening in t-h-t, I have some question regarding the pacemaker things. If we take rabbitmq: - we have rabbitmq things in docker/services - we have rabbitmq things in puppet/services - we have rabbitmq things in docker/services/pacemaker - we have rabbitmq things in puppet/services/pacemaker If the plain services are easy to flatten, the pacemaker part is more annoying, at least on the naming/location. I see the following possibilities: - create a deployment/pacemaker and move all pacemaker-related things in there - name files something like rabbitmq-pacemaker-foo.yaml and push them in deployment/rabbitmq Both look valid. And both might have their downsides. Any advice, idea, feeling on that? Also, regarding the workflow: do we do that flattening in one, or two passes? i.e. we can move all rabbitmq related code at once, or only the plain service, and do a second patch for the pacemaker things. Here again, both look valid, but I'm more in the "2 passes" idea. So... yeah, I'd like to get some feedback on that in order to do things right, and avoid monkey-patching because paths/naming aren't good ;). Thanks! Cheers, C. -- Cédric Jeanneret Software Engineer DFG:DF

2 1

can't login to a compute node deployed using ironic
by Manuel Sopena Ballesteros 18 Dec '18

18 Dec '18

3 2

Meaning of role name: auditor versus reader
by Adam Young 18 Dec '18

18 Dec '18

We've recently come to accept reader as one of the default roles. However, one thing that is not clear to me is the intention: is this designed to be the readonly set of operations that an admin can do, or the read only set of operations that a member can do? Should we really have two read-only roles, one for each case? Perhaps the admin-read-only should be called auditor, and then reader is for member only operations?

4 4

[KOLLA][MONASCA] monasca containers not running
by Manuel Sopena Ballesteros 18 Dec '18

18 Dec '18

Dear Openstack and Kolla community, I am trying to deploy monasca using kolla-ansible 7.0.0 and realised a couple of containers are not working Container monasca_log_persister See: 'bin/logstash --help' + sudo -E kolla_set_configs INFO:__main__:Loading config file at /var/lib/kolla/config_files/config.json INFO:__main__:Validating config file INFO:__main__:Kolla config strategy set to: COPY_ALWAYS INFO:__main__:Copying service configuration files INFO:__main__:Deleting /etc/logstash/conf.d/log-persister.conf INFO:__main__:Copying /var/lib/kolla/config_files/log-persister.conf to /etc/logstash/conf.d/log-persister.conf INFO:__main__:Setting permission for /etc/logstash/conf.d/log-persister.conf INFO:__main__:Deleting /etc/logstash/elasticsearch-template.json INFO:__main__:Copying /var/lib/kolla/config_files/elasticsearch-template.json to /etc/logstash/elasticsearch-template.json INFO:__main__:Setting permission for /etc/logstash/elasticsearch-template.json INFO:__main__:Writing out command to execute INFO:__main__:Setting permission for /var/log/kolla/monasca INFO:__main__:Setting permission for /var/log/kolla/monasca/monasca-api-error.log INFO:__main__:Setting permission for /var/log/kolla/monasca/monasca-api-access.log INFO:__main__:Setting permission for /var/log/kolla/monasca/monasca-log-api-error.log INFO:__main__:Setting permission for /var/log/kolla/monasca/monasca-log-api-access.log ++ cat /run_command + CMD='/usr/share/logstash/bin/logstash --log-in-json --log /var/log/kolla/monasca/monasca-log-persister.log -f /etc/logstash/conf.d/log-persister.conf' + ARGS= + [[ ! -n '' ]] + . kolla_extend_start ++ [[ ! -d /var/log/kolla/logstash ]] +++ stat -c %a /var/log/kolla/logstash ++ [[ 755 != \7\5\5 ]] + echo 'Running command: '\''/usr/share/logstash/bin/logstash --log-in-json --log /var/log/kolla/monasca/monasca-log-persister.log -f /etc/logstash/conf.d/log-persister.conf'\''' Running command: '/usr/share/logstash/bin/logstash --log-in-json --log /var/log/kolla/monasca/monasca-log-persister.log -f /etc/logstash/conf.d/log-persister.conf' + exec /usr/share/logstash/bin/logstash --log-in-json --log /var/log/kolla/monasca/monasca-log-persister.log -f /etc/logstash/conf.d/log-persister.conf WARNING: Could not find logstash.yml which is typically located in $LS_HOME/config or /etc/logstash. You can specify the path using --path.settings. Continuing using the defaults ERROR: Unrecognised option '--log-in-json' Container monasca_log_transformer See: 'bin/logstash --help' + sudo -E kolla_set_configs INFO:__main__:Loading config file at /var/lib/kolla/config_files/config.json INFO:__main__:Validating config file INFO:__main__:Kolla config strategy set to: COPY_ALWAYS INFO:__main__:Copying service configuration files INFO:__main__:Deleting /etc/logstash/conf.d/log-transformer.conf INFO:__main__:Copying /var/lib/kolla/config_files/log-transformer.conf to /etc/logstash/conf.d/log-transformer.conf INFO:__main__:Setting permission for /etc/logstash/conf.d/log-transformer.conf INFO:__main__:Writing out command to execute INFO:__main__:Setting permission for /var/log/kolla/logstash ++ cat /run_command + CMD='/usr/share/logstash/bin/logstash --log-in-json --log /var/log/kolla/logstash/monasca-log-transformer.log -f /etc/logstash/conf.d/log-transformer.conf' + ARGS= + [[ ! -n '' ]] + . kolla_extend_start ++ [[ ! -d /var/log/kolla/logstash ]] +++ stat -c %a /var/log/kolla/logstash ++ [[ 755 != \7\5\5 ]] + echo 'Running command: '\''/usr/share/logstash/bin/logstash --log-in-json --log /var/log/kolla/logstash/monasca-log-transformer.log -f /etc/logstash/conf.d/log-transformer.conf'\''' Running command: '/usr/share/logstash/bin/logstash --log-in-json --log /var/log/kolla/logstash/monasca-log-transformer.log -f /etc/logstash/conf.d/log-transformer.conf' + exec /usr/share/logstash/bin/logstash --log-in-json --log /var/log/kolla/logstash/monasca-log-transformer.log -f /etc/logstash/conf.d/log-transformer.conf WARNING: Could not find logstash.yml which is typically located in $LS_HOME/config or /etc/logstash. You can specify the path using --path.settings. Continuing using the defaults ERROR: Unrecognised option '--log-in-json' Any thoughts? Thank you very much Manuel Sopena Ballesteros | Big data Engineer Garvan Institute of Medical Research The Kinghorn Cancer Centre, 370 Victoria Street, Darlinghurst, NSW 2010 T: + 61 (0)2 9355 5760 | F: +61 (0)2 9295 8507 | E: manuel.sb(a)garvan.org.au<mailto:manuel.sb@garvan.org.au> NOTICE Please consider the environment before printing this email. This message and any attachments are intended for the addressee named and may contain legally privileged/confidential/copyright information. If you are not the intended recipient, you should not read, use, disclose, copy or distribute this communication. If you have received this message in error please notify us at once by return email and then delete both messages. We accept no liability for the distribution of viruses or similar in electronic communications. This notice should not be removed.

2 1

Instance Unable to connect to Data/Management Network
by Zufar Dhiyaulhaq 18 Dec '18

18 Dec '18

Hi, I have OpenStack cluster with this following network environment. Global Configuration : Data & Management Network : 10.60.60.0/24 External Network: 10.61.61.0/24 - All my endpoint is created in the Data & Management Network - Instance get floating IP from External Network IP Address Allocation : Controller: 10.60.60.10 | 10.61.61.10 Compute0: 10.60.60.20 | 10.61.61.20 Compute1: 10.60.60.30 | 10.61.61.30 Floating IP range : 10.61.61.100 - 10.61.61.200 My problem is the Instance cannot connect (ping, ssh, all connection) into the data/management network. I am running a magnum cluster but the instance needs to communicate with the endpoint. How to allow an Instance to connect to the data/management network? Best Regards, Zufar Dhiyaulhaq

2 1

[dev] [tc][all] TC office hours is started now on #openstack-tc
by Ghanshyam Mann 18 Dec '18

18 Dec '18

Hello everyone, TC office hour is started on #openstack-tc channel. Feel free to reach to us for anything you want discuss/input/feedback/help from TC. - gmann & TC

1 0