Dear Developers
I have one question.
Can be create instance and network by RESTful API ?
I would like to know “How to create Instance and Network” by RESTful API.
Figure.
[External Linux-based Server] -- OpenStack RESTful API > [OpenStack
Controller Server]
If you have ideas, please
On 20/06/13 22:19 -0400, cbjc...@linux.vnet.ibm.com wrote:
So anyway, let's get back to the topic this thread was discussing
about - "passing meta data into provider stacks".
It seems that we have all reached an agreement that deletepolicy and
updatepolicy will be passed as params, and metad
On 06/20/2013 10:18 PM, Russell Bryant wrote:
> On 06/20/2013 10:36 AM, Giorgio Franceschi wrote:
>> Hello, I created a blueprint for the implementation of:
>>
>> A tool for pinning automatically each running virtual CPU to a physical
>> one in the most efficient way, balancing load across sockets/
On 06/21/2013 09:45 AM, L Radhakrishna Rao wrote:
> Hi All,
>
> I am glad to be the member of this group.
>
> I am looking forward to contribute to open stack, in all possible ways.
Did you take a look at this? "all possible ways" are listed here --
http://wiki.openstack.org/HowToContribute
Jus
Hi All,
I am glad to be the member of this group.
I am looking forward to contribute to open stack, in all possible ways.
Kindly let me know how to get started.
And please, bear with me if I ask questions which are too easy for you all.
With Best Regards,
Radhakrishna
So anyway, let's get back to the topic this thread was discussing
about - "passing meta data into provider stacks".
It seems that we have all reached an agreement that deletepolicy and
updatepolicy will be passed as params, and metadata will be exposed to
provider templates through a func
Something has been struggling to the surface of my brain since our last
talk.
It should not be inherited 'roles' but rather:
"users in this group should get role X in all projects in a domain."
It is the group to role mapping that we need to fix. Right now, we can
add a group to a role in a
On Jun 20, 2013, at 5:36 PM, Christopher Yeoh wrote:
> The management of security groups can be handled through the
> project-formerly-known-as-quantum, but the (dis)association of security
> groups to instances does I think need to be handled by Nova. So we'll need
> the SecurityGroupActionCon
Hi Melanie,
Looking at the security groups extensions I think that it will after all be
necessary to port part of the extension from V2.
The management of security groups can be handled through the
project-formerly-known-as-quantum, but the (dis)association of security
groups to instances does I
I liked the idea of not storing the tokens and keystone will verify the
validity by signature. Expiry time can still be set for the generated token
however we want.
On Thu, Jun 20, 2013 at 1:50 PM, Ali, Haneef wrote:
> **1) **I’m really not sure how that will solve the original issue
> (To
On Thu, 2013-06-20 at 16:02 -0400, Sean Dague wrote:
> There are lots of nice things we could do, given time and people. But
> the reality is that relatively few people are actually working on the
> API code, documentation, tooling around it.
>
> I would much rather have us deliver a world class
Could it be possible to add a flag to disable the allocation for the IP?
If the "no allocation" flag is enabled, all ports will have an empty value
for IPs.
It will increase the config parameters in quantum, should we try it?
Edgar
From: Mark McClain
Reply-To: OpenStack List
Date: Thursday,
1) I’m really not sure how that will solve the original issue (Token table
size increase). Of course we can have a job to remove the expired token.
2) We really have to think how the other services are using keystone.
Keystone “createToken” volume is going to increase. Fixing one iss
There's work under way to make IP allocation pluggable. One of the options will
include not having an allocator for a subnet.
mark
On Jun 20, 2013, at 2:36 PM, Edgar Magana wrote:
> Developers,
>
> So far in Networking (formerly Quantum) IPs are pre-allocated when a new port
> is created by
There are lots of nice things we could do, given time and people. But
the reality is that relatively few people are actually working on the
API code, documentation, tooling around it.
I would much rather have us deliver a world class JSON API with
validation and schema and comprehensive testin
I may spend some time on this subject, so please share your script if you
can so that I can look through it and see what can be done to provide some
automated gating.
On Thu, Jun 20, 2013 at 11:44 PM, Jeremy Stanley wrote:
> On 2013-06-20 15:56:22 +0400 (+0400), Dina Belova wrote:
> > I'm writi
On 6/20/13 4:21 AM, Sean Dague wrote:
The following patch review came into Tempest yesterday to stop checking
for specific 20x codes on a number of Swift API -
https://review.openstack.org/#/c/33689/
The official documentation for these APIs says the following -
http://docs.openstack.org/api/ope
Agreed, never said anything was intentional and I understand that, things
just evolve and that¹s how it works.
But instead of further diverging (2 things in oslo) it seems better to
organize and work together instead of against right?
Maybe taskflow can help make that possible, maybe it can't, bu
On 2013-06-20 15:56:22 +0400 (+0400), Dina Belova wrote:
> I'm writing to suggest that git-review requires to be covered by
> tests. There are no testing part in it at all, so maybe it is a
> good idea to cover it.
[...]
(Cc'ing you since I'm unsure whether you're subscribed, but setting
MFT to th
Hi all,
The [state-management] project team holds a weekly meeting in
#openstack-meeting on thursdays, 2000 UTC. The next meeting is today, June
20!!! (sorry this was late in coming out)
As usual, everyone is welcome :-)
Link: https://wiki.openstack.org/wiki/Meetings/StateManagement
## Agenda
Joshua,
On Jun 20, 2013, at 12:34 PM, Joshua Harlow
wrote:
> Thanks Adrian for adding that,
>
> Zane, it would be great if you could show up. I have a few questions about
> said heat requirements, especially about how the current mechanism
> accomplishes those requirements.
>
> IMHO I'd rathe
Thanks Adrian for adding that,
Zane, it would be great if you could show up. I have a few questions about
said heat requirements, especially about how the current mechanism
accomplishes those requirements.
IMHO I'd rather not have 2 workflow libraries (aka your scheduler.py) and
taskflow. It woul
Me too, that was sort of awesome.
I also wish we could get rid of XML but that might be primarily because I find
it awkward to work with the way it is now.
As was mentioned before, I think the main thing is making it easier to support.
The autogeneration idea is great.
On Jun 20, 2013, at 4:10
Previously discussed:
http://lists.openstack.org/pipermail/openstack-dev/2013-May/008436.html
tl;dr Don't do any of that!
-Dolph
On Wed, Jun 19, 2013 at 7:31 PM, Frittoli, Andrea (Cloud Services) <
fritt...@hp.com> wrote:
> Hi folks,
>
> ** **
>
> While reviewing nova v3 tests, I realize
Thanks everyone who have joined today's Savanna meeting.
Here are the logs from today's meeting:
Minutes:
http://eavesdrop.openstack.org/meetings/savanna/2013/savanna.2013-06-20-18.04.html
Minutes (text):
http://eavesdrop.openstack.org/meetings/savanna/2013/savanna.2013-06-20-18.04.txt
Log:
ht
+1
On Thu, Jun 20, 2013 at 11:37 AM, Dolph Mathews wrote:
>
> On Wed, Jun 19, 2013 at 2:20 PM, Adam Young wrote:
>
>> I really want to go the other way on this: I want token to be very
>> short lived, ideally something like 1 minute, but probably 5 minutes to
>> account for clock skew. I want
On Thu, Jun 20, 2013 at 10:51 AM, Russell Bryant wrote:
> On 06/20/2013 11:20 AM, Brian Elliott wrote:
> > On Jun 19, 2013, at 7:34 PM, Christopher Yeoh wrote:
> >
> >> Hi,
> >>
> >> Just wondering what people thought about how necessary it is to keep
> XML support for the Nova v3 API, given tha
Developers,
So far in Networking (formerly Quantum) IPs are pre-allocated when a new
port is created by the following def:
_allocate_ips_for_port(self, context, network, port):
If we are using a real DHCP (not the dnsmasq process) that does not accept
static IP allocation because it only allocate
On Wed, Jun 19, 2013 at 2:20 PM, Adam Young wrote:
> I really want to go the other way on this: I want token to be very
> short lived, ideally something like 1 minute, but probably 5 minutes to
> account for clock skew. I want to get rid of token revocation list
> checking. I'd like to get aw
There are existing mappings for this, like JSONx, but I don't think that's the
right approach. You lose the benefits of having XML at that point -- no
namespaces, etc. What you need to find is a nice middle ground, where you get
benefits from XML, but you don't have to deal with a lot of the s
On Jun 20, 2013, at 10:22 AM, Brant Knudson wrote:
> How about a mapping of JSON concepts to XML like:
>
> collections:
> the-value ...
> the-value ...
>
> values:
> text
>
>
>
> number
>
> This type of mapping would remove any ambiguities. Ambiguities and complexity
> are problem
On 06/20/2013 01:22 PM, Brant Knudson wrote:
How about a mapping of JSON concepts to XML like:
collections:
the-value ...
the-value ...
values:
text
number
This type of mapping would remove any ambiguities. Ambiguities and
complexity are problems I've seen with the XML-JSON mapping
How about a mapping of JSON concepts to XML like:
collections:
the-value ...
the-value ...
values:
text
number
This type of mapping would remove any ambiguities. Ambiguities and
complexity are problems I've seen with the XML-JSON mapping in Keystone.
Plus the fact that it's so not-XML
On 06/20/2013 01:02 PM, John Garbutt wrote:
> Hi,
>
> I have had some discussions about if I should add a config flag in this
> change:
> https://review.openstack.org/#/c/32760/
>
> I am looking to support adding a large amount of ephemeral disk space
> to a VM, but the VHD format has a limit of
We spoke about some nice validation frameworks at the summit, and here
and there.
Could we get away with XML->JSON then validate the JSON request (and
assume XML parse error also means bad request)?
John
On 20 June 2013 17:44, Russell Bryant wrote:
> On 06/20/2013 12:00 PM, Thierry Carrez wrote
Hi,
I have had some discussions about if I should add a config flag in this change:
https://review.openstack.org/#/c/32760/
I am looking to support adding a large amount of ephemeral disk space
to a VM, but the VHD format has a limit of around 2TB per disk. To
work around this in XenServer, I pla
On 06/20/2013 12:00 PM, Thierry Carrez wrote:
> Christopher Yeoh wrote:
>> Just wondering what people thought about how necessary it is to keep XML
>> support for the Nova v3 API, given that if we want to drop it doing so
>> during the v2->v3 transition is pretty much the ideal time to do so.
>
>
On 06/20/2013 10:36 AM, Giorgio Franceschi wrote:
> Hello, I created a blueprint for the implementation of:
>
> A tool for pinning automatically each running virtual CPU to a physical
> one in the most efficient way, balancing load across sockets/cores and
> maximizing cache sharing/minimizing cac
Folks,
Is anyone having troubles running the units tests locally on a clean venv
with both run-tests.sh and tox?
I found out that this is relevant to the issue I am seeing:
https://answers.launchpad.net/quantum/+question/230219
I cannot go past the ML2 unit tests, namely only 1900~ tests run, a
Zane,
Thanks for putting the requirements list together. That's very helpful. There
is a task-flow meeting today where we can discuss this. I added it to the
agenda. Please attend if possible:
https://wiki.openstack.org/wiki/Meetings/StateManagement
Thanks,
Adrian
On Jun 20, 2013, at 8:48 AM
On Jun 20, 2013, at 10:51 AM, Russell Bryant wrote:
> On 06/20/2013 11:20 AM, Brian Elliott wrote:
>> On Jun 19, 2013, at 7:34 PM, Christopher Yeoh wrote:
>>
>>> Hi,
>>>
>>> Just wondering what people thought about how necessary it is to keep XML
>>> support for the Nova v3 API, given that if
Perfect.
On Thu, Jun 20, 2013 at 5:20 AM, Thierry Carrez wrote:
> Mark Washenberger wrote:
> > This sounds like a fantastic improvement. I'd really like to have a
> > "next" milestone as well as an "Ongoing" milestone, for tracking the
> > kinds of long, drawn out refactorings / code improvement
Something similar was discussed a while back on this channel:
http://lists.openstack.org/pipermail/openstack-dev/2013-May/008752.html
See if it helps.
Cheers,
Armando
On Wed, Jun 5, 2013 at 1:11 PM, Jani, Nrupal wrote:
> Hi there,
>
> ** **
>
> I am little new to the openstack networking
Christopher Yeoh wrote:
> Just wondering what people thought about how necessary it is to keep XML
> support for the Nova v3 API, given that if we want to drop it doing so
> during the v2->v3 transition is pretty much the ideal time to do so.
Although I hate XML as much as anyone else, I think it
After the Heat meeting yesterday I had a discussion with Keith Bray and
Jessica Lucci about what sort of features Heat needs from TaskFlow in
order to be able to adopt it as a workflow system. In the course of that
discussion I volunteered to put together a list of requirements, and
here is my
On 06/20/2013 11:20 AM, Brian Elliott wrote:
> On Jun 19, 2013, at 7:34 PM, Christopher Yeoh wrote:
>
>> Hi,
>>
>> Just wondering what people thought about how necessary it is to keep XML
>> support for the Nova v3 API, given that if we want to drop it doing so
>> during the v2->v3 transition i
On Thu, 2013-06-20 at 10:04 +0930, Christopher Yeoh wrote:
> Just wondering what people thought about how necessary it is to keep
> XML support for the Nova v3 API, given that if we want to drop it
> doing so during the v2->v3 transition is pretty much the ideal time to
> do so.
>
> The current pl
Removed completely... No longer needed
Ilya Shakhat wrote:
>Hi Monty,
>
>
>I've noticed that pbr section of Quantum's setup.cfg contains misspelled
>parameter:
>
>[pbr]
>
>single-version-externally-mananged = true
>
>(extra 'n' in word managed)
>
>Should this parameter be fixed or removed compl
On Jun 19, 2013, at 7:34 PM, Christopher Yeoh wrote:
> Hi,
>
> Just wondering what people thought about how necessary it is to keep XML
> support for the Nova v3 API, given that if we want to drop it doing so during
> the v2->v3 transition is pretty much the ideal time to do so.
>
> The curre
Hi Community,
The first release of Murano - Windows DataCenter as a Service
implementation for OpenStack is published. A distribution package is
available on Launchpad. From the functionality standpoint it has all the
features targeted for 0.1 version.
The key features are:
-
Active Direc
Hi David,
Yes, that is another way of describing it. I think, for IceHouse, there are a
number of discussion to be had around whether role should stay a simple
name/id, or whether it should have structure/attributes. There is already one
proposal to give it a ServiceID, another we have often
The idea of health-monitor templates was first discussed here:
http://lists.openstack.org/pipermail/openstack-dev/2012-November/003233.html
See follow-up on that mailing list thread to understand pro and cons of the
idea.
I will avoid moaning about backward compatibility at the moment, but that
so
It's a bug, this is the code in pbr that references it:
https://github.com/openstack-dev/pbr/blob/master/pbr/packaging.py#L304
Good catch.
I've opened bug https://bugs.launchpad.net/quantum/+bug/1192987 .
Thanks,
MATT RIEDEMANN
Advisory Software Engineer
Cloud Solutions and OpenStack Develop
Hello, I created a blueprint for the implementation of:
A tool for pinning automatically each running virtual CPU to a physical
one in the most efficient way, balancing load across sockets/cores and
maximizing cache sharing/minimizing cache misses. Ideally able to be run
on-demand, as a periodic
The work described below has been completed with a few changes from the
original description. This change is for nova only.
1. The require_admin_context has been removed in cases where it overrode
the policy set in policy.json
2. Error handling has been cleaned up. All calls shoul
Hi,
I agree with this.
We are facing challenges when the global health pool is changed to atomically
modify all the groups that are linked to this health check as the groups might
be configured in different devices.
So if one of the group modification fails it is very difficult to revert the
ch
On Thu, 2013-06-20 at 07:21 -0400, Sean Dague wrote:
> The following patch review came into Tempest yesterday to stop checking
> for specific 20x codes on a number of Swift API -
> https://review.openstack.org/#/c/33689/
>
> The official documentation for these APIs says the following -
> http:
Mark Washenberger wrote:
> This sounds like a fantastic improvement. I'd really like to have a
> "next" milestone as well as an "Ongoing" milestone, for tracking the
> kinds of long, drawn out refactorings / code improvements that cannot
> fit in a single milestone but still need to be communicated
Hi community,
Here's a question.
Currently Health monitors in Loadbalancer service are made in such way that
health monitor itself is a global shared database object.
If user wants to add health monitor to a pool, it adds association between
pool and health monitor.
In order to update existing hea
Hello!
I'm writing to suggest that git-review requires to be covered by tests.
There are no testing part in it at all, so maybe it is a good idea to cover
it.
There are two types of tests to be implemented to cover the project:
* unit tests to verify working of the separated methods
* integrated
The following patch review came into Tempest yesterday to stop checking
for specific 20x codes on a number of Swift API -
https://review.openstack.org/#/c/33689/
The official documentation for these APIs says the following -
http://docs.openstack.org/api/openstack-object-storage/1.0/content/re
You had me going there for a minute, Jay!
-- dims
On Thu, Jun 20, 2013 at 1:07 AM, Jay Pipes wrote:
> On 06/20/2013 12:09 AM, Jorge Williams wrote:
>>
>> There was a presentation by Pete Johnson in the San Diego summit about
>> what we're missing in OpenStack for enterprises and good support fo
Hi Monty,
I've noticed that pbr section of Quantum's setup.cfg contains misspelled
parameter:
*[pbr]*
*single-version-externally-mananged = true*
(extra 'n' in word managed)
Should this parameter be fixed or removed completely?
Ilya
___
OpenStack-dev ma
Hi, guys,
When I port hypervisor extension into Nova API v3, I found some actions
doesn't follow REST principles.
But I still have some doubt. So I send mail to here, hope I can get some
suggestion.
Let me explain why I want to change those API.
For search action: https://review.openstack.or
Hi Don.
On Tue 18 Jun 2013 (04:14), Dugger, Donald D wrote:
> 1) Scalability issues, specifically sending utilization data through the DB
> or via RPC call
> 2) Follow ups on the scheduler BPs
> 3) Opens?
>
> PS: The list of scheduler BPs is:
I wanted to join the meeting but unfortunately I
On 06/19/2013 09:39 PM, Abhishek Chanda wrote:
Hi all,
Is there an official guide to migrate nova network plugins to quantum
plugins (or rather, neutron plugins)?
Hi,
Sadly we have not made much progress with this. There are a number of
issues to consider when moving from traditional nova ne
Hi Henry
I (think I) understand what you are trying to do. To rephrase it from a
different angle, you are trying to assign virtual roles in projects that
currently dont exist, to users now, so that when these projects may
eventually come into existence, these users will automatically have real
Yes this is a good reply that addresses my point.
The reason that I am being cautious is that in general, white lists are
better than black lists and positive grants are better than negative
ones (since you can always list what you specifically want to allow, but
cannot usually list what you d
Hi,
Just a reminder that we have a list of proposed features to move into or
out of the V3 API core.
https://etherpad.openstack.org/NovaV3APICore
If you at all care about what is core and what isn't please have a look and
vote +1/-1 along with your name.
Anything that doesn't have a -1 next to
Hi.
We're trying to configure Quantum REST Proxy Plugin to use an external
Network service developed by ourselves in the context of OpenNaaS Project
[1]. We have developed a REST server to listen Proxy requests. We want to
modify Plugin configuration as described in OpenStack official
documentatio
70 matches
Mail list logo
