Re: [Netstack] [Openstack] Compute API and doc
Hi Netstackers - Yes, Dan has outlined the basic benefits to the separate repo. In the case of the network-api repository (is that the right name?), the OpenStack doc-core team does have the ability to vote +2 in addition to the core netstack team. That doc-core team is me, David Cramer, and Kevin Bringard. We all understand the voting and review process and won't push something through without the right votes, though. :) For the admin manual, which I'm very pleased about, we can house it in the openstack-manuals project with the other admin manuals and publish to docs.openstack.org/incubation. The review system on that project is set for the doc-core team to review those manuals but any other votes are also welcomed. Thanks, Anne *Anne Gentle* a...@openstack.org my blog <http://justwriteclick.com/> | my book<http://xmlpress.net/publications/conversation-community/>| LinkedIn <http://www.linkedin.com/in/annegentle> | Delicious<http://del.icio.us/annegentle>| Twitter <http://twitter.com/annegentle> On Wed, Sep 28, 2011 at 1:46 PM, Dan Wendlandt wrote: > Hi folks, > > Anne's suggestion is to have Quantum follow the other OpenStack projects > and have our API docs in a separate repo. This has the benefit of keeping > the large docbook diffs out of the main repo, but has the downside that it > may be harder to enforce that code & API docs are in sync. > > Unless someone has concerns here, we'll follow the standard path. > > Anne, I assume that the same core team is responsible for approving changes > to the API docs? > > Dan > > > On Wed, Sep 14, 2011 at 10:20 AM, Dan Wendlandt wrote: > >> All major openstack projects seem to be heading in the direction of >> keeping their API documentation in a separate repo. >> >> Salvatore, what are your thoughts on taking this approach with Quantum? >> Any one else see pluses or minus, other than the obvious benefit of mapping >> to what other OpenStack projects are doing? >> >> My assumption is that the api repo is managed by the core team, just like >> the main code repo. >> >> Dan >> >> -- Forwarded message -- >> From: Anne Gentle >> Date: Wed, Sep 14, 2011 at 9:45 AM >> Subject: [Openstack] Compute API and doc >> To: openst...@lists.launchpad.net >> >> >> Hi all - >> >> The move to Github for the Compute API is now complete and the 1.1 API >> spec, the 1.0 API doc, and the API Extension proposal now live in this >> repository: >> >> https://github.com/openstack/compute-api >> >> There's also a new Jenkins job that builds the documents to >> docs.openstack.org/trunk out of this repo. >> >> Next I'll move the rest of the books out of the Launchpad >> openstack-manuals repository, though you can continue to log doc bugs in >> Launchpad at http://bugs.launchpad.net/openstack-manuals. >> >> Thanks for hanging in there through the transition. >> >> Anne >> >> >> ___ >> Mailing list: https://launchpad.net/~openstack >> Post to : openst...@lists.launchpad.net >> Unsubscribe : https://launchpad.net/~openstack >> More help : https://help.launchpad.net/ListHelp >> >> >> >> >> -- >> ~~~ >> Dan Wendlandt >> Nicira Networks, Inc. >> www.nicira.com | www.openvswitch.org >> Sr. Product Manager >> cell: 650-906-2650 >> ~~~ >> >> > > > -- > ~~~ > Dan Wendlandt > Nicira Networks, Inc. > www.nicira.com | www.openvswitch.org > Sr. Product Manager > cell: 650-906-2650 > ~~~ > > -- Mailing list: https://launchpad.net/~netstack Post to : netstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~netstack More help : https://help.launchpad.net/ListHelp
[Netstack] OpenStack Quantum documentation
Hi Dan and all - All the doc files should be tucked snugly into the correct repos, but Jenkins is pouting about the build job right now. Still, that's fixable and I'm just waiting for the CI team to take a look and fix it. Once that's done, any changes to these source files are automatically sent to http://docs.openstack.org/incubation. Source for the Quantum Admin Manual: http://github.com/openstack/openstack-manuals Source for Quantum API 1.0 Manual: http://github.com/openstack/netconn-api I've also set up a Disqus comment identifier for the Quantum manuals, so that you can choose moderators for those doc comments. It's * os-quantum-guides and it's embedded in the pom.xml file. Please sign up for a Disqus account so I can add you as moderator for these comments, also so that email will come to you when someone comments on a doc page. You can also subscribe to this RSS feed for the doc comments: **http://** os-quantum-guides.disqus.com/latest.rss*. Let me know if you have any questions, and welcome to the fancy DocBook doc build system we have. :) Anne *Anne Gentle* a...@openstack.org my blog <http://justwriteclick.com/> | my book<http://xmlpress.net/publications/conversation-community/>| LinkedIn <http://www.linkedin.com/in/annegentle> | Delicious<http://del.icio.us/annegentle>| Twitter <http://twitter.com/annegentle> -- Mailing list: https://launchpad.net/~netstack Post to : netstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~netstack More help : https://help.launchpad.net/ListHelp
Re: [Netstack] VM creation error in Devstack
Hi guys - Well, I'm pleased to report that we anticipated the need for subscribing to changes to a particular manual, and the "Release History" table fulfills that requirement by offering an RSS feed. However looks like we need to troubleshoot it a bit as it's not working right now. I'm logging a bug about it, https://bugs.launchpad.net/openstack-manuals/+bug/937206. For the Quantum Admin guide, the feed is linked to the orange RSS button in the row next to the PDF button on http://docs.openstack.org/incubation/openstack-network/admin/content/. Authors should be conscious of the need for informative, readable notes in the Revision History table as those are published to the feed. I'll let you know how the bug fixing goes. Thanks, Anne On Mon, Feb 20, 2012 at 1:52 PM, Dan Wendlandt wrote: > > > On Wed, Feb 8, 2012 at 11:17 AM, Sumit Naiksatam (snaiksat) > wrote: >> >> Hi Dan, >> >> Thanks for the clarifying this, and also kudos for keeping the >> documentation in sync. While on this, is there a way to subscribe to changes >> in the Quantum documentation (or better still, subscribe the netstack >> mailer)? I think that might help to preempt these kind of issues. The >> general tendency is to read the documentation on the first setup, and not as >> often after that, thus missing some of these changes. > > > Hi Sumit, > > I think that's a good suggestion. Unfortunately, the simple approach of > just subscribing the list to notifications for changes in the docs repo > doesn't work well, as that repo is actually shared across all openstack > projects. Of course, that doesn't stop anyone from also subscribing to the > openstack-manuals repo using gerrit, but it does mean that there's more > traffic than I would like to force to the netstack list. One other approach > might be to just try and push any proposed docs diffs to the netstack list. > This would be good both for notifying users of quantum, and for getting > folks to help review docs changes :) > > I'm CC'ing Anne to see if she has input. > > dan > > >> >> >> Thanks, >> ~Sumit. >> >> > -Original Message- >> > From: netstack-bounces+snaiksat=cisco@lists.launchpad.net >> > [mailto:netstack-bounces+snaiksat=cisco@lists.launchpad.net] On >> > Behalf Of Dan Wendlandt >> > Sent: Tuesday, February 07, 2012 8:36 PM >> > To: Shweta Padubidri (shpadubi) >> > Cc: netstack@lists.launchpad.net >> > Subject: Re: [Netstack] VM creation error in Devstack >> > >> > Hi Shweta, >> > >> > Thanks for the detailed report, this is very helpful. >> > >> > With some recent changes in nova, you can no longer specify the >> > project "name" in the --project_id flag for a network. You must >> > specify the keystone "id". This keystone id for the admin tenant >> > would be "ba2436c876564ef985a094a4f71b61c2", and you can use the when >> > you create a network with nova-manage. See: >> > http://docs.openstack.org/incubation/openstack- >> > network/admin/content/Net-Create-dle455.html >> > . Note: a recent change (in keystone?) meant that keystone ids >> > switched from being integers to uuids, so the example in the docs >> > should be updated to show an example with --project_id= . >> > >> > Let me know if that helps. >> > >> > Dan >> > >> > On Tue, Feb 7, 2012 at 7:08 PM, Shweta Padubidri (shpadubi) >> > wrote: >> > > Hi Dan, >> > > >> > > Thanks for the email. >> > > >> > > Sure, this is what I did. After the devstack install >> > > >> > > I created a vm in the default tenant >> > > TENANT= >> > > USERNAME= >> > > . openrc >> > > nova boot --flavor 1 --image eeb1801e-a143-4669-96e5-55f753ad26bd >> > def_vm1 >> > > >> > > The vm was created. >> > > >> > > Next I created a network in the admin tenant and then placed a vm in >> > that network. >> > > >> > > nova-manage --flagfile=/opt/stack/nova/bin/nova.conf network create >> > --label=admin-net1 --fixed_range_v4=10.0.10.0/24 --project_id=admin -- >> > priority=1 >> > > TENANT=admin >> > > USERNAME=admin >> > > . openrc >> > > nova boot --flavor 1 --image eeb1801e-a143-4669-96e5-55f753ad26bd -- >> > nic net-id=b1f828c1-d769-4aab-a77a-c999e3b49ecf admin_nw1_vm1 >> > > >> > > So here is the tenant and the network list >> > > >> > > This is the tenant list >> > > ~/devstack$ /opt/stack/keystone/bin/keystone-manage tenant list >> > > --- >> > > | Tenants | >> > > --- >> > > | id | name | enabled | >> > > --- >> > > | ba2436c876564ef985a094a4f71b61c2 | admin | True | >> > > | ea1170fdb1df4023aad9c39ff1b85a7d | demo | True | >> > > | d6d48b0112eb47d48702a9c04ebcc98d | invisible_to_admin | True | >> > > --- >> > > >> > > Thi
Re: [Netstack] VM creation error in Devstack
Hi all - I fixed this bug this morning, the Jenkins server wasn't copying any XML files at all so the atom.xml got lost in the automated build process. Woops. It's all fixed now. You may want to add more informative messages in the Revision History table so that details like the --project_id flag for a network is explicitly spelled out. Thanks, Anne On Mon, Feb 20, 2012 at 2:03 PM, Anne Gentle wrote: > Hi guys - > > Well, I'm pleased to report that we anticipated the need for > subscribing to changes to a particular manual, and the "Release > History" table fulfills that requirement by offering an RSS feed. > However looks like we need to troubleshoot it a bit as it's not > working right now. I'm logging a bug about it, > https://bugs.launchpad.net/openstack-manuals/+bug/937206. > > For the Quantum Admin guide, the feed is linked to the orange RSS > button in the row next to the PDF button on > http://docs.openstack.org/incubation/openstack-network/admin/content/. > > Authors should be conscious of the need for informative, readable > notes in the Revision History table as those are published to the > feed. > > I'll let you know how the bug fixing goes. > > Thanks, > Anne > > > On Mon, Feb 20, 2012 at 1:52 PM, Dan Wendlandt wrote: >> >> >> On Wed, Feb 8, 2012 at 11:17 AM, Sumit Naiksatam (snaiksat) >> wrote: >>> >>> Hi Dan, >>> >>> Thanks for the clarifying this, and also kudos for keeping the >>> documentation in sync. While on this, is there a way to subscribe to changes >>> in the Quantum documentation (or better still, subscribe the netstack >>> mailer)? I think that might help to preempt these kind of issues. The >>> general tendency is to read the documentation on the first setup, and not as >>> often after that, thus missing some of these changes. >> >> >> Hi Sumit, >> >> I think that's a good suggestion. Unfortunately, the simple approach of >> just subscribing the list to notifications for changes in the docs repo >> doesn't work well, as that repo is actually shared across all openstack >> projects. Of course, that doesn't stop anyone from also subscribing to the >> openstack-manuals repo using gerrit, but it does mean that there's more >> traffic than I would like to force to the netstack list. One other approach >> might be to just try and push any proposed docs diffs to the netstack list. >> This would be good both for notifying users of quantum, and for getting >> folks to help review docs changes :) >> >> I'm CC'ing Anne to see if she has input. >> >> dan >> >> >>> >>> >>> Thanks, >>> ~Sumit. >>> >>> > -Original Message- >>> > From: netstack-bounces+snaiksat=cisco@lists.launchpad.net >>> > [mailto:netstack-bounces+snaiksat=cisco@lists.launchpad.net] On >>> > Behalf Of Dan Wendlandt >>> > Sent: Tuesday, February 07, 2012 8:36 PM >>> > To: Shweta Padubidri (shpadubi) >>> > Cc: netstack@lists.launchpad.net >>> > Subject: Re: [Netstack] VM creation error in Devstack >>> > >>> > Hi Shweta, >>> > >>> > Thanks for the detailed report, this is very helpful. >>> > >>> > With some recent changes in nova, you can no longer specify the >>> > project "name" in the --project_id flag for a network. You must >>> > specify the keystone "id". This keystone id for the admin tenant >>> > would be "ba2436c876564ef985a094a4f71b61c2", and you can use the when >>> > you create a network with nova-manage. See: >>> > http://docs.openstack.org/incubation/openstack- >>> > network/admin/content/Net-Create-dle455.html >>> > . Note: a recent change (in keystone?) meant that keystone ids >>> > switched from being integers to uuids, so the example in the docs >>> > should be updated to show an example with --project_id= . >>> > >>> > Let me know if that helps. >>> > >>> > Dan >>> > >>> > On Tue, Feb 7, 2012 at 7:08 PM, Shweta Padubidri (shpadubi) >>> > wrote: >>> > > Hi Dan, >>> > > >>> > > Thanks for the email. >>> > > >>> > > Sure, this is what I did. After the devstack install >>> > > >>> > > I created a vm in the default tenant >>> > > TENAN
[Netstack] Fwd: [Openstack] Interaction between nova and melange : ip fixed not found
Hi all -
I'm not sure how people found these melange policy create commands -
is there a doc plan for Melange commands such as those described here?
I read through the API doc housed on github but wasn't sure how CLI
commands are handled.
Thanks in advance for some clarity,
Anne
-- Forwarded message --
From: Jason Kölker
Date: Tue, Feb 28, 2012 at 9:31 AM
Subject: Re: [Openstack] Interaction between nova and melange : ip
fixed not found
To: openst...@lists.launchpad.net
On Tue, 2012-02-28 at 11:52 +0100, Jérôme Gallard wrote:
> Hi all,
>
> I use the trunk version of Nova, Quantum (with the OVS plugin) and Melange.
> I created networks, everything seems to be right.
>
> I have two questions :
> - the first VM I boot takes always a wrong IP address (for instance
> 172.16.0.0). However, when I boot a second VM, this one takes a good
> IP (for instance 172.16.0.2). Do you know why this can happened ?
The default melange policy allows assignment of the network address and
synthesise a gateway address (if it is not specified). It will not hand
out the gateway address. The "fix" is to create an ip policy that
restricts the octect 0. I think the syntax is something like
`melange policy create -t {tennant} name={block_name}
desc={policy_name}` (This should return the policy_id for the next
command)
`melange unusable_ip_octet create -t {tennant} policy_id={policy_id}
octect=0`
`melange ip_block update -t {tennant} id={block_id}
policy_id={policy_id}`
> - I have an error regarding an fixed IP not found. Effectively, when I
> check the nova database, the fixed_ip table is empty but as I am using
> quantum and melange and their tables seems to be nicely filled. Do you
> have an idea about this issue ?
> This is a copy/paste of the error:
> 2012-02-28 10:45:53 DEBUG nova.rpc.common [-] received
> {u'_context_roles': [u'admin'], u'_context_request_id':
> u'req-461788a6-3570-4fa9-8620-6705eb69243c', u│··
> '_context_read_deleted': u'no', u'args': {u'address': u'172.16.0.2'},
> u'_context_auth_token': None, u'_context_strategy': u'noauth',
> u'_context_is_admin': Tr│··
> ue, u'_context_project_id': None, u'_context_timestamp':
> u'2012-02-28T09:45:53.484445', u'_context_user_id': None, u'method':
> u'lease_fixed_ip', u'_context_r│··
> emote_address': None} from (pid=8844) _safe_log
> /usr/local/src/nova/nova/rpc/common.py:144 │··
> 2012-02-28 10:45:53 DEBUG nova.rpc.common
> [req-461788a6-3570-4fa9-8620-6705eb69243c None None] unpacked context:
> {'request_id': u'req-461788a6-3570-4fa9-8620│··
> -6705eb69243c', 'user_id': None, 'roles': [u'admin'], 'timestamp':
> '2012-02-28T09:45:53.484445', 'is_admin': True, 'auth_token': None,
> 'project_id': None, 'r│··
> emote_address': None, 'read_deleted': u'no', 'strategy': u'noauth'}
> from (pid=8844) unpack_context
> /usr/local/src/nova/nova/rpc/amqp.py:187 │··
> 2012-02-28 10:45:53 DEBUG nova.network.manager
> [req-461788a6-3570-4fa9-8620-6705eb69243c None None] Leased IP
> |172.16.0.2| from (pid=8844) lease_fixed_ip
> /us│··r/local/src/nova/nova/network/manager.py:1186 │··
> 2012-02-28 10:45:53 ERROR nova.rpc.common [-] Exception during message
> handling │··(nova.rpc.common): TRACE: Traceback (most recent call
> last): │··
> (nova.rpc.common): TRACE: File "/usr/local/src/nova/nova/rpc/amqp.py",
> line 250, in _process_data │··(nova.rpc.common): TRACE: rval =
> node_func(context=ctxt, **node_args) │··(nova.rpc.common): TRACE: File
> "/usr/local/src/nova/nova/network/manager.py", line 1187, in
> lease_fixed_ip │··(nova.rpc.common): TRACE: fixed_ip =
> self.db.fixed_ip_get_by_address(context, address) │··
> (nova.rpc.common): TRACE: File "/usr/local/src/nova/nova/db/api.py",
> line 473, in fixed_ip_get_by_address │··(nova.rpc.common): TRACE:
> return IMPL.fixed_ip_get_by_address(context, address)
> │··(nova.rpc.common): TRACE: File
> "/usr/local/src/nova/nova/db/sqlalchemy/api.py", line 119, in wrapper
> │··
> (nova.rpc.common): TRACE: return f(*args, **kwargs)
> │··(nova.rpc.common): TRACE: File
> "/usr/local/src/nova/nova/db/sqlalchemy/api.py", line 1131, in
> fixed_ip_get_by_address │··
> (nova.rpc.common): TRACE: raise
> exception.FixedIpNotFoundForAddress(address=address) │··
> (nova.rpc.common): TRACE: FixedIpNotFoundForAddress: Fixed ip not
> found for address 172.16.0.2. │··
> (nova.rpc.common): TRACE:
You need to create your networks through nova-manage, otherwise the nova
tables don't get filled in. The next release we are axing the nova
tables as it was just a crutch to get it "usable".
Happy Hacking!
7-11
___
Mailing list: https://launchpad.net/~openstack
Post to : openst...@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
--
Mailing list: https://launchpad.net/~netstack
Post to : netstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~netstack
More help : https://help.launchpad.net/ListHelp
