[Openstack-operators] [Metadata in Neutron]
Hi everyone. Neutron uses two ways to supply metadata via DHCP_agent or L3_agent. So what situation do we use metadata via dhcp_agent or L3_agent? Can you guide me how config to supply metadata via DHCP_agent? ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
[Openstack-operators] User requirements feedback loop
In preparation for the summit, the user committee has been reviewing how the various teams and working groups around operators, end users and ecosystem developers could be structured. In particular, how we can turn the ideas into actionable items and expand the activities given the growth in the user community. In preparation for the summit, we would welcome feedback from those interested in enhancing the requirements to implementation feedback loop on the mailing list. The details are in https://etherpad.openstack.org/p/uc-2015. We'll have a session at the summit to discuss aat https://etherpad.openstack.org/p/YVR-ops-user-committee but I'd be happy to incorporate mailing list discussion into the agenda and report back after the event. Thanks, Tim, Jon, Subbu and Tom ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
[Openstack-operators] Federation Ops Session at the Vancouver Summit
Hello, Following suit of the other posts, this is an announcement / reminder of the Federation Ops Session happening next Tuesday: http://sched.co/3BBs The etherpad for the session is here: https://etherpad.openstack.org/p/YVR-ops-federation I encourage everyone to add items they'd like to discuss prior to the Session, but if you don't get to it, just bring it up during the Session -- we'll most likely be able to fit it in. Thanks, Joe ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
Re: [Openstack-operators] chef
On May 12, 2015, at 10:06 AM, Abel Lopez alopg...@gmail.com wrote: I think the error comes from your chef server, not openstack API. Have you tried answering N to the overwrite? On May 12, 2015, at 4:48 AM, aishwarya.adyanth...@accenture.com mailto:aishwarya.adyanth...@accenture.com wrote: Hello, I’m trying to integrate chef-server(version 11.0.10) with Ubuntu Openstack. I’m able to create an instance from the chef server in the openstack dashboard but I get an error while trying to bootstrap the node. The error is as described below: root@master:~/chef-repo# knife bootstrap external_ip –i /home/oss/chef_key.pem -x ash --sudo -V INFO: Using configuration from /root/chef-repo/.chef/knife.rb Node exists, overwrite it? (Y/N) y INFO: HTTP Request Returned 405 Method Not Allowed: ERROR: Method Not Allowed Response: I configured security rules in the dashboard by adding http, https, ssh but it doesn’t seem to work. Can someone tell me what I’m doing wrong? Thanks in advance! Aishwarya Adyanthaya Hi! Ashwarya, any chance can you come around to #openstack-chef on freenode? We have a great community there and I’m betting we can help move you forward with your issue. If you’d like to directly ping me i’m j^2 in the channel, and am almost always there. And to parriot what Abel is saying it looks like that issue is related to you not removing the node from your chef server, but we can talk more detail there. Best Regards, JJ Asghar c: 512.619.0722 t: @jjasghar ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
[Openstack-operators] [openstack-operators][chef] OpenStack-Chef Ops Meetup
Hey Everyone! I’d like to announce the OpenStack-Chef Ops Meetup in Vancouver. We have an etherpad[1] going with topics people would like to discuss. I haven’t found a room or space for us yet, but when I do I’ll comment back on this thread and add it to the etherpad, (right now looking at the other declaration of time slots, I think Wednesday 1630 is going to be our best bet) As with the Paris Ops Meetup we had a lot of great questions and use cases discussed but it was very unstructured and I got some negative feedback about that, hence the etherpad. I’d like to leverage the etherpad and have a semi-solid agenda so we can hit any major discussion topics that you, the community, would like to discuss. If I can ask for a volunteer note-taker to step up and to directly contact me; so when we start the meeting we can just jump in that would me amazing. I can sweeten the deal if you step up with some Chef Swag too ;). I hope to see you there and don’t hesitate to reach out if you have any relevant questions. Best Regards, JJ Asghar c: 512.619.0722 t: @jjasghar [1]: https://etherpad.openstack.org/p/YVR-ops-chef https://etherpad.openstack.org/p/YVR-ops-chef ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
Re: [Openstack-operators] chef
Hi, While I try to answer “N” to the overwrite this is what I get: root@master:~/chef-repo# knife bootstrap external_ip –i /home/oss/chef_key.pem -x ash --sudo -V INFO: Using configuration from /root/chef-repo/.chef/knife.rb Node exists, overwrite it? (Y/N) n You said no, so I'm done here. root@master:~/chef-repo# My knife.rb reads like this: log_level :info log_location STDOUT node_name 'ash' client_key '/root/chef-repo/.chef/ash.pem' validation_client_name'chef-validator' validation_key '/root/chef-repo/.chef/chef-validator.pem' chef_server_url 'https://master:443' syntax_check_cache_path '/root/chef-repo/.chef/syntax_check_cache' cookbook_path [ '/root/chef-repo/cookbooks' ] ### Note: If you are not proxying HTTPS to the OpenStack auth port, the scheme should be HTTP knife[:openstack_auth_url] = http://controller:5000/v2.0/tokens; knife[:openstack_username] = admin knife[:openstack_password] = admin knife[:openstack_tenant] = admin root@master:~/chef-repo/.chef# ls admin.pem ash.pem knife.rb syntax_check_cache trusted_certs From: Abel Lopez [mailto:alopg...@gmail.com] Sent: Tuesday, May 12, 2015 8:36 PM To: Adyanthaya, Aishwarya Cc: openstack-operators@lists.openstack.org Subject: Re: [Openstack-operators] chef I think the error comes from your chef server, not openstack API. Have you tried answering N to the overwrite? On May 12, 2015, at 4:48 AM, aishwarya.adyanth...@accenture.commailto:aishwarya.adyanth...@accenture.com wrote: Hello, I’m trying to integrate chef-server(version 11.0.10) with Ubuntu Openstack. I’m able to create an instance from the chef server in the openstack dashboard but I get an error while trying to bootstrap the node. The error is as described below: root@master:~/chef-repo# knife bootstrap external_ip –i /home/oss/chef_key.pem -x ash --sudo -V INFO: Using configuration from /root/chef-repo/.chef/knife.rb Node exists, overwrite it? (Y/N) y INFO: HTTP Request Returned 405 Method Not Allowed: ERROR: Method Not Allowed Response: I configured security rules in the dashboard by adding http, https, ssh but it doesn’t seem to work. Can someone tell me what I’m doing wrong? Thanks in advance! Aishwarya Adyanthaya This message is for the designated recipient only and may contain privileged, proprietary, or otherwise confidential information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the e-mail by you is prohibited. Where allowed by local law, electronic communications with Accenture and its affiliates, including e-mail and instant messaging (including content), may be scanned by our systems for the purposes of information security and assessment of internal compliance with Accenture policy. __ www.accenture.comhttp://www.accenture.com/ ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.orgmailto:OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
Re: [Openstack-operators] [Metadata in Neutron]
The metadata on DHCP agent is only provided when you have isolated networks, that means “networks with no router attached”. And it’s only enabled if you set True enable_isolated_metadata in /etc/neutron/dhcp_agent.ini Let me know if that works for you. Best regards, Miguel Ángel. Miguel Ángel Ajo On Tuesday, 12 de May de 2015 at 10:16, Nam Nguyễn Hoài wrote: Hi everyone. Neutron uses two ways to supply metadata via DHCP_agent or L3_agent. So what situation do we use metadata via dhcp_agent or L3_agent? Can you guide me how config to supply metadata via DHCP_agent? ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org (mailto:OpenStack-operators@lists.openstack.org) http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
Re: [Openstack-operators] [Metadata in Neutron]
Thanks for your answer. I want to combine two usecases that are Per-tenant router with private networks architecture and Single flat network. Metadata is supplied via DHCP_agent (I solved metadata with your guide) and Single flat network supply IP external network for instance but instance can not connect external network. Can you guide me config this case. http://prntscr.com/74mo5z 2015-05-12 15:48 GMT+07:00 Miguel Ángel Ajo majop...@redhat.com: The metadata on DHCP agent is only provided when you have isolated networks, that means “networks with no router attached”. And it’s only enabled if you set True enable_isolated_metadata in /etc/neutron/dhcp_agent.ini Let me know if that works for you. Best regards, Miguel Ángel. Miguel Ángel Ajo On Tuesday, 12 de May de 2015 at 10:16, Nam Nguyễn Hoài wrote: Hi everyone. Neutron uses two ways to supply metadata via DHCP_agent or L3_agent. So what situation do we use metadata via dhcp_agent or L3_agent? Can you guide me how config to supply metadata via DHCP_agent? ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
[Openstack-operators] Introducing the Ops Tags Team
Hi all, By now you should have seen Thierry's The Way Forward blog[1], which describes the problems with having just one binary flag to say whether a project is 'good' or not (the integrated release), and proposes the tags system. The tags system lets us make up a series of labels for each software project in the OpenStack ecosystem to help people in their decision making. As Ops, we have a lot of knowledge about what works, and how it works. We're also in a good position to define what it is our fellow Ops actually needed to know before they choose to deploy something. It's my great pleasure to announce the formation of the Ops Tag Team. Continuing from the initial work done by the user committee and those of us who made it to Philadelphia[2], the Vancouver summit is the time to really get this effort ramped up. The team will have a working session to define the initial set of tags. There are a range of questions you likely have, and many an effort needed on scoping this activity to be the most useful it can be. I've attempted to kick-start some things on the etherpad for that session, and your edits and tag suggestions there would be appreciated: https://etherpad.openstack.org/p/YVR-ops-tags Please do make that etherpad as useful as possible :) The room we have at the summit is limited in size, and really designed for those who plan to make ongoing contributions to the activity to do actual work. Regards, Tom, on behalf of the User Committee [1] http://ttx.re/the-way-forward.html [2] https://etherpad.openstack.org/p/PHL-ops-tags ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
