Port profile is generic way of Neutron to pass plugin-specific data
as dictionary. Cisco plugin uses it to pass VMEFX specific data.
Robert, correct me if I'm wrong.
thanks,
---
Isaku Yamahata isaku.yamah...@gmail.com
On Thu, Oct 31, 2013 at 10:21:20PM +,
Jiang, Yunhong
Hi,
I wanted to build an application on openstack and wanted help on how do i
go about doing it? Since i am absolutely new to the stack I was wondering
if their is a developer's manual or something of that sort.
All I have done so far is started the installation of devstack. I am typing
this
It depends on what kind of application your are building. There serveral
way of developing something above openstack services.
I hope this wikinpage would help you a bit
https://wiki.openstack.org/wiki/Documentation
2013/11/2 Krishanu Dhar rony.k...@gmail.com
Hi,
I wanted to build an
Sorry for being vague in my previous email. Thanks for the link, I'll go
through it.
I am trying to build an app that resides on the cloud and would want to
perform some basic storage management operations.
On Sat, Nov 2, 2013 at 3:07 PM, Denis Makogon dmako...@mirantis.com wrote:
It depends
I am trying to build an app that resides on the cloud and would want to
perform some basic storage management operations. br/br/So, you want to
build an app atop Swift ?br/br/-Romainbr/___
OpenStack-dev mailing list
Ok, i got it. I'd suggest you to describe whole copcent of your application
(if it is not commercial secret) and let community lead you to right
direction.
There simple rules of developing with OpenStack:
1. Python based.
2. Clinet/Server interaction
3. ReST
4. Test coverage. Inner test or
Migrations from Essex to Grizzly/Havana
...
I would find it entirely suitable to upgrade from Essex to Folsom, then
migrate from nova-volume to cinder and from nova-network to quantum, then
only to upgrade to Grizzly.
We're in the same spot, upgrading an Essex deployment to Havana. We
On 11/01/2013 11:02 AM, Dean Troyer wrote:
To clarify a bit, while deprecated, nova-network has not lost any
functionality in Havana yet. It also hasn't gained much (if any), but
it still works. The majority of the testing is performed using
nova-network and not neutron (yet).
It is also
On 11/01/2013 05:50 PM, Michael Still wrote:
On Sat, Nov 2, 2013 at 3:30 AM, Russell Bryant rbry...@redhat.com wrote:
I also would not use migrate. sqlalchemy-migrate is a dead upstream and
we (OpenStack) have had to inherit it. For new projects, you should use
alembic. That's actively
On 11/01/2013 12:46 PM, Clayton Coleman wrote:
I was also going to throw in migrate as a dependency and put in the glue
code for that based on common use from ironic/trove/heat. That'll pull in
a few openstack common and config settings. Finally, was going to add a
solum-dbsync command a la
Sphoorti,
Just copying the list with some pointers on this issue that
I gave you on IRC.
Running 'neutron router-update' show that the tenant ID is absent
from the 'router.update.start' but present in the 'router.update.end'
notification.
Note that the logic to send the update.start
On 11/01/2013 09:55 PM, Noorul Islam K M wrote:
I was looking at the review [1]. And at that point I vaguely remembered
a discussion on IRC about framework choice for WSGI. But those
discussions are not captured in document and brought to conclusion. So,
I think it will be great, if we create
On 11/01/2013 04:58 AM, Steven Hardy wrote:
On Thu, Oct 31, 2013 at 09:40:46PM -0400, Adam Young wrote:
snip
I think it is safe to say that the trusts API is broken in XML. I
added the following test:
diff --git a/keystone/tests/test_v3_auth.py b/keystone/tests/test_v3_auth.py
index
Hi all,
One of the most important aspects in the early stages of Solum
development will be the consensus building and stabilization of the
Solum API specification. A solid API spec aid in the speeding up the
pace of innovation in the Solum contributor community.
One of the aspects of the
On Sat, Nov 2, 2013 at 4:39 PM, Jay Pipes jaypi...@gmail.com wrote:
Hi all,
One of the most important aspects in the early stages of Solum development
will be the consensus building and stabilization of the Solum API
specification. A solid API spec aid in the speeding up the pace of
Jay,
On Nov 2, 2013, at 2:39 PM, Jay Pipes jaypi...@gmail.com wrote:
Hi all,
One of the most important aspects in the early stages of Solum development
will be the consensus building and stabilization of the Solum API
specification. A solid API spec aid in the speeding up the pace of
+1 - with the level of interest among existing vendors I think this will help
others who want to be API compatible with Solum (above and beyond normal
benefits)
On Nov 2, 2013, at 5:48 PM, Jay Pipes jaypi...@gmail.com wrote:
Hi all,
One of the most important aspects in the early stages
Team,
The dates have been chosen based on your feedback:
https://wiki.openstack.org/wiki/Solum/BreakoutMeetings#Solum_API_Deep_Dive
Please mark your calendars for 2100 UTC on 2013-11-13 and 2013-11-15. We will
meet in #solum.
Thanks,
Adrian
On Oct 31, 2013, at 11:35 AM, Adrian Otto
+1 Couldn't agree more.
Christopher Armstrong chris.armstr...@rackspace.com wrote:
On Sat, Nov 2, 2013 at 4:39 PM, Jay Pipes
jaypi...@gmail.commailto:jaypi...@gmail.com wrote:
Hi all,
One of the most important aspects in the early stages of Solum development will
be the consensus building
Thanks for diving into this one guys! Very much appreciated.
-Sean
On 11/02/2013 02:22 AM, Armando Migliaccio wrote:
I think/hope I nailed it down. Once more patch coming right up!
On Fri, Nov 1, 2013 at 11:15 AM, Salvatore Orlando sorla...@nicira.comwrote:
Hi Sean,
I looked
On 11/02/2013 11:54 AM, Adrian Otto wrote:
Noorul,
I agree that key decisions should be tracked in blueprints. This is the
one for this decision which was made in our 2013-10-18 public meeting.
Jay's submission is consistent with the direction indicated by the team.
On 10/30/2013 11:35 PM, Daniel P. Berrange wrote:
On Wed, Oct 30, 2013 at 04:20:34AM -0400, Russell Bryant wrote:
On 10/30/2013 03:13 AM, Alex Glikson wrote:
Maybe a more appropriate approach could be to have a tool/script that
does it, as a one time thing.
For example, it could make sense in
On 10/30/2013 11:51 PM, Mike Spreitzer wrote:
Swapnil Kulkarni swapnilkulkarni2...@gmail.com wrote on 10/30/2013
02:36:37 AM:
I had a discussion with russellb regarding this for yesterday, I
would like to discuss this with the team regarding the blueprint
mentioned in subject.
My thoughts exactly. I meant to dig into the soft-delete code to see if those
changes handled resource_id differently but I got to traveling and forgot. IMO,
if it universally needs doing, then it should be done in resource.Resource and
be cognizant of deletion policy.
On 10/31/2013 04:45 AM, Alan Kavanagh wrote:
Sorry Russell but I have to ask, what is the different you see between
traditional datacenter virtualization and cloud. IMHO the two co-exist
and Cloud (the buzz word that it is) is the umbrella for all encompassing
data center. That said im
On 11/02/2013 01:42 AM, Adrian Otto wrote:
Team,
We have a blueprint for logging architecture within Solum, which is an
important feature to aid in debugging at runtime:
https://blueprints.launchpad.net/solum/+spec/logging
The Implementation field of the blueprint says Needs Code Review,
Hi OpenStackers,
We've been working on an open policy framework for OpenStack that we're calling
Congress. We've been talking with OpenStack users and several of our partners
to understand the kinds of rules and regulations they envision enforcing with a
policy-based management framework.
Zen, Kevin, Aaron, Salvatore et al,
Thank you so much for taking some time and reviewing this proposal. I
couldn't get any time slot neither in Neutron nor Heat track to have a deep
discussion about this proposal. My conclusions are the following:
- This API should be allocated in Heat project,
Thanks Denis. So,this is what I am planning.
An application; I was thinking of writing it up in java 'coz I ain't that
good in python. It could be accessed either via a web browser or an app
could be downloaded to a desktop.
Brief set of functionalities...
1. A db backend to store information
29 matches
Mail list logo
