Thanks Somik,
One question: in the "Quantum-Dashboard workflow today", what determines
how many vNICs a VM is given?
In general, I see a couple key areas for improvement in the network
workflow:
- Be able to use the Dashboard to create a network with a specified subnet.
Under the covers, this w
On Wed, Sep 28, 2011 at 5:38 PM, Salvatore Orlando <
salvatore.orla...@eu.citrix.com> wrote:
> Hi Somik,
>
> ** **
>
> These are exactly the kind of questions I would like to answer in the
> session I have proposed.
>
> I don’t think we need to schedule a different session in the unconfe
Hi Somik,
These are exactly the kind of questions I would like to answer in the session I
have proposed.
I don't think we need to schedule a different session in the unconference.
I hope we can use this thread to precisely define the agenda of the session.
Salvatore
From: netstack-bounces+salv
Hi all,
I have some notes inline for you.
On Sep 28, 2011, at 2:59 PM, Somik Behera wrote:
> Hi All,
>
> I just wanted to send few initial thoughts on enhancing our Dashboard
> integration to better enable the end-user(tenant) to manage their networking(
> L2, IPAM all together) as well as pr
Hi All,
I just wanted to send few initial thoughts on enhancing our Dashboard
integration to better enable the end-user(tenant) to manage their
networking( L2, IPAM all together) as well as provide the Cloud Admin a
location, where they can interact with Quantum, and perform Quantum specific
funct
Hi,
I'm completely happy to align Quantum with the other Openstack projects, and
move the API documentation in a separate repo.
I'm totally fine with granting +2 rights to doc-core team, and I believe that
their reviews will be of great help to improve the quality of the documentation.
Salvat
On Wed, Sep 28, 2011 at 11:54 AM, Anne Gentle wrote:
> 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
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
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.
Unles
1. Overview of vision for project
a. discussion
2. Technical discussion
a. Api
b. model
3. working groups
a. call for volunteers
b. plan for summit
signature.asc
Description: OpenPGP digital signature
--
Mailing list: https://launchpad.net/~netstack
Post to : netstack@lists.launchpa
10 matches
Mail list logo