It is not a problem to update the code in given direction when the
decision is made. As I understood right now it's not about the code -
that's why I'd canceled the code review until the blueprint is accepted
- it's more about architecture and procedures such as which tests should
be obligatory
04.12.2013 11:57, Christopher Yeoh ?:
On Wed, Dec 4, 2013 at 5:22 PM, Alexandre Levine
mailto:alev...@cloudscaling.com>> wrote:
It is not a problem to update the code in given direction when the
decision is made. As I understood right now it's not about the
code -
Russell,
I'm a little confused about importing it into stackforge repository.
Please clarify it for me.
Right now our code is a part of nova itself, adding lots of files and
changing several of existing, namely: service.py, cmd/api.py, setup.cfg,
api-paste.ini and nova.conf.sample. This is onl
ous questions.
Alex
10.12.2013 18:56, Russell Bryant пишет:
On 12/10/2013 08:47 AM, Christopher Yeoh wrote:
On Tue, Dec 10, 2013 at 11:36 PM, Alexandre Levine
mailto:alev...@cloudscaling.com>> wrote:
Russell,
I'm a little confused about importing it into stackforge repository
0.12.2013 17:47, Christopher Yeoh ?:
On Tue, Dec 10, 2013 at 11:36 PM, Alexandre Levine
mailto:alev...@cloudscaling.com>> wrote:
Russell,
I'm a little confused about importing it into stackforge
repository. Please clarify it for me.
Right now our code is a part of nova it
Ok, Russell, if we do go this way creating a separate project what would
be the correct naming for it in openstack?
gce-api, gce-compat, gce or some cryptic name like GraCE or GraCEful,
for example? :)
Alex
10.12.2013 22:14, Russell Bryant пишет:
On 12/10/2013 11:13 AM, Alexandre Levine
This thread is created in regard to newly introduced EC2 API standalone
service effort which is covered by the following:
Blueprint:
https://blueprints.launchpad.net/nova/+spec/ec2-api
Nova spec:
https://review.openstack.org/#/c/147882
Project and code:
https://github.com/stackforge/ec2-api
K
Cristopher,
FYI in regard to "
Its the sort of direction that we tried to steer the GCE
API folks in I
cehouse, though I don't know what they ended up doing
"
We ended up perfectly ok. The project is on Stackforge for some time
https://github.com/stackforge/gce-api. It works.
I believe that t
m
not sure what it takes and means to commit to this - we'll discuss it as
well.
Best regards,
Alex Levine
24.04.2014 23:33, Joe Gordon ?:
On Thu, Apr 24, 2014 at 10:10 AM, Alexandre Levine
mailto:alev...@cloudscaling.com>> wrote:
Cristopher,
FYI in regard to "
Hi All,
I'm looking for a way to set port_filter flag to False for port binding.
Is there a way to do this in IceHouse or in current Juno code? I use
devstack with the default ML2 plugin and configuration.
According to this guide
(http://docs.openstack.org/api/openstack-network/2.0/content/b
Sorry,
I managed to misplace my question into the existing thread.
On 9/26/14, 12:56 AM, Alexandre Levine wrote:
Hi All,
I'm looking for a way to set port_filter flag to False for port
binding. Is there a way to do this in IceHouse or in current Juno
code? I use devstack with the de
Hi All,
I'm looking for a way to set port_filter flag to False for port binding.
Is there a way to do this in IceHouse or in current Juno code? I use
devstack with the default ML2 plugin and configuration.
According to this guide
(http://docs.openstack.org/api/openstack-network/2.0/content/b
rts and if needed we can spare even more resources to help
with the refactoring in the next cycle.
Best regards,
Alex Levine
On 5/10/16 7:40 PM, Matt Riedemann wrote:
On 5/10/2016 11:24 AM, Alexandre Levine wrote:
Hi Matt,
Sorry I couldn't reply earlier - was away.
I'm wo
Hi Matt,
Sorry I couldn't reply earlier - was away.
I'm worrying about ScaleIO ephemeral storage backend
(https://blueprints.launchpad.net/nova/+spec/scaleio-ephemeral-storage-backend)
which is not in this list but various clients are very interested in
having it working along with or instead
Thank you Matt.
We'll think how we can help here.
Best regards,
Alex Levine
On 5/10/16 7:40 PM, Matt Riedemann wrote:
On 5/10/2016 11:24 AM, Alexandre Levine wrote:
Hi Matt,
Sorry I couldn't reply earlier - was away.
I'm worrying about ScaleIO ephemeral storage
Hi all,
os-user-data extension implements server_create method to add user_data
for server creation. No Controller is used for this, only "class
UserData(extensions.V21APIExtensionBase)".
I want to add server_update method allowing to update the user_data.
Obviously I have to add it as a mic
Hi all,
os-user-data extension implements server_create method to add user_data
for server creation. No Controller is used for this, only "class
UserData(extensions.V21APIExtensionBase)".
I want to add server_update method allowing to update the user_data.
Obviously I have to add it as a mic
let me know if you have
any trouble with this.
Thanks
Alex
2015-12-13 2:34 GMT+08:00 Alexandre Levine
mailto:alexandrelev...@gmail.com>>:
Hi all,
os-user-data extension implements server_create method to add
user_data for server creation. No Co
Thierry,
The ec2-api project is in gating and totally functional. We'll apply for
it to become OpenStack project very shortly. Next week in fact.
Best regards,
Alex Levine
On 1/8/16 9:47 AM, Thierry Carrez wrote:
Davanum Srinivas wrote:
Dear Nova cores,
Sorry this did not make into the
I've created a review: https://review.openstack.org/#/c/268774/
Best regards,
Alex Levine
On 1/8/16 3:45 PM, Thierry Carrez wrote:
Alexandre Levine wrote:
The ec2-api project is in gating and totally functional. We'll apply for
it to become OpenStack project very shortly. Next we
Hi everybody,
There is a problem using keystone v3 in Kilo by external EC2 API service. The
problem doesn't exist for keystone v2 and it is fixed in master for keystone v3
by the following patch:
https://github.com/openstack/python-keystoneclient/commit/f6ab133f25f00e041cd84aa8bbfb422594d1942f
Thank you Dolph.
Best regards,
Alex Levine
On 8/13/15 4:02 PM, Dolph Mathews wrote:
https://review.openstack.org/#/c/212515/
On Thu, Aug 13, 2015 at 6:57 AM, Alexandre Levine
mailto:alexandrelev...@gmail.com>> wrote:
Hi everybody,
There is a problem using keystone v3 in K
Hi Matthew,
I'd like to provide you with some info in regard to standalone EC2 API part.
I can't claim clear understanding of tempest development directions but
here are the things to take in account about EC2 API:
1. Standalone EC2 API carry all of its tests including previously
tempest ones
Hi all,
I'd like to bring up this matter again, although it was at some extent
discussed during the recent summit.
The problem arises from the fact that the functionality exposing device
names for usage through public APIs is deteriorating in nova. It's being
deliberately removed because as
ola Đipanov wrote:
On 05/27/2015 09:47 AM, Alexandre Levine wrote:
Hi all,
I'd like to bring up this matter again, although it was at some extent
discussed during the recent summit.
The problem arises from the fact that the functionality exposing device
names for usage through public APIs
commented on some of the bugs above and provided a small
patch that I think fixes one bit of it. As described on the bug - device
names might be a bit trickier, but I hope to have something posted next
week.
Help with testing (while patches are in review) would be hugely appreciated!
On 05/28/2
Hi all,
I wanted to remind everybody that the existing nova's EC2 API was
deprecated in Kilo and the replacement-to-be (stackforge/ec2-api) stays
virtually untouched by customers. It means that without real beta and
production testing it's not going to get accepted into OpenStack. Since
nova'
Hi everybody,
My name is Alex Levine and I'm the current PTL of EC2 project.
Apparently I have to apologize for everybody because being in this role
for just less than a month I didn't expect I have to go through
elections for the newborn project so I haven't even looked at this side.
When I'd
Thank you Randy, you've summed up what I explained in the other thread.
Yes I promise to keep up a good work as EC2 PTL in the next cycle if I'm
appointed.
Best regards,
Alex Levine
On 3/21/16 2:07 AM, Bias, Randy wrote:
Hello,
First of all, let me apologize for answering on Alex Lev
Doug,
Let me clarify a bit the situation.
Before this February there wasn't such a project at all. EC2 API was a
built-in part of nova so no dedicated PTL was required. The built-in
part got removed and our project got promoted. We're a team of 3
developers which nevertheless are committed to
Thomas,
I'm the lead of the team working on it.
The project is in a release-candidate state and the EC2 (non-VPC) part
is just being finished, so there are no tags or branches yet. Also we
were not sure about what should we do with it since we were told that
it'll have a chance of going as a p
Michael,
Our team can take the effort. We're the ones doing the stackforge EC2
API and we can maintain the nova's EC2 in acceptable state for the time
being as well.
If you can give us any permissions and leverage to not just contribute
fixes and tests but also have a say in approval of those
gnificant problem in
production.
I think this would merit a good slot in the Vancouver design sessions
so we can also discuss documentation, migration, packaging,
configuration management, scaling, HA, etc.
Tim
*From:*matt [mailto:m...@nycresistor.com]
*Sent:* 30 January 2015 20:44
*To:*
Davanum,
Now that the picture with the both EC2 API solutions has cleared up a
bit, I can say yes, we'll be adding the tempest tests and doing devstack
integration.
Best regards,
Alex Levine
On 1/31/15 2:21 AM, Davanum Srinivas wrote:
Alexandre, Randy,
Are there plans afoot to add suppor
e via extensions or versioning and we can see what we're dealing with
we also can be independent in terms of releases.
Best regards,
Alex Levine
On 1/31/15 1:37 AM, Matt Riedemann wrote:
On 1/29/2015 5:52 AM, Alexandre Levine wrote:
Thomas,
I'm the lead of the team working on it.
Daniel,
On 2/2/15 12:58 PM, Daniel P. Berrange wrote:
On Fri, Jan 30, 2015 at 07:57:08PM +, Tim Bell wrote:
Alex,
Many thanks for the constructive approach. I've added an item to the list for
the Ops meetup in March to see who would be interested to help.
As discussed on the change,
,
Very cool. thanks.
-- dims
On Sat, Jan 31, 2015 at 1:04 AM, Alexandre Levine
wrote:
Davanum,
Now that the picture with the both EC2 API solutions has cleared up a bit, I
can say yes, we'll be adding the tempest tests and doing devstack
integration.
Best regards,
Alex Levine
On 1/31/
Thank you Sean.
We'll be tons of EC2 Tempest tests for your attention shortly.
How would you prefer them? In several reviews, I believe. Not in one, right?
Best regards,
Alex Levine
On 2/2/15 6:55 PM, Sean Dague wrote:
On 02/02/2015 07:01 AM, Alexandre Levine wrote:
Michael,
I
On 2/2/15 7:39 PM, Sean Dague wrote:
On 02/02/2015 11:35 AM, Alexandre Levine wrote:
Thank you Sean.
We'll be tons of EC2 Tempest tests for your attention shortly.
How would you prefer them? In several reviews, I believe. Not in one,
right?
Best regards,
Alex Levine
So, honestly, I
On 2/2/15 7:04 PM, Sean Dague wrote:
On 02/02/2015 07:01 AM, Alexandre Levine wrote:
Michael,
I'm rather new here, especially in regard to communication matters, so
I'd also be glad to understand how it's done and then I can drive it if
it's ok with everybody.
By saying EC
On 2/2/15 8:30 PM, Matthew Treinish wrote:
On Mon, Feb 02, 2015 at 07:35:46PM +0300, Alexandre Levine wrote:
Thank you Sean.
We'll be tons of EC2 Tempest tests for your attention shortly.
How would you prefer them? In several reviews, I believe. Not in one, right?
Let's take a ste
On 2/2/15 11:15 PM, Michael Still wrote:
On Mon, Feb 2, 2015 at 11:01 PM, Alexandre Levine
wrote:
Michael,
I'm rather new here, especially in regard to communication matters, so I'd
also be glad to understand how it's done and then I can drive it if it's ok
with everybod
I'm writing this in regard to several reviews concering tagging
functionality for EC2 API in nova.
The list of the reviews concerned is here:
https://review.openstack.org/#/q/status:open+project:openstack/nova+branch:master+topic:bp/ec2-volume-and-snapshot-tags,n,z
I don't think it's a good ide
ory.
Best regards,
Alex Levine
On 2/4/15 4:32 PM, Rushi Agrawal wrote:
Thanks Alex for your detailed inspection of my work. Comments inline..
On 3 February 2015 at 21:32, Alexandre Levine
mailto:alev...@cloudscaling.com>> wrote:
I'm writing this in regard to several reviews
Davanum,
We've added the devstack support. It's in our stackforge repository.
https://github.com/stackforge/ec2-api/tree/master/contrib/devstack
Best regards,
Alex Levine
On 1/31/15 2:21 AM, Davanum Srinivas wrote:
Alexandre, Randy,
Are there plans afoot to add support to switch on stackfor
:
On 02/05/2015 07:01 AM, Alexandre Levine wrote:
> Davanum,
>
> We've added the devstack support. It's in our stackforge repository.
> https://github.com/stackforge/ec2-api/tree/master/contrib/devstack
>
> Best regards,
> Alex Levi
sub group in Nova for EC2 APIs and start the
weekly meetings, reviews, code cleanup, etc tasks.
Will update the same on wiki page also soon..
Thanks
Swami
On Fri, Feb 6, 2015 at 9:27 PM, David Kranz wrote:
On 02/06/2015 07:49 AM, Sean Dague wrote:
On 02/06/2015 07:39 AM, Alexandre Levine wr
at 9:50 PM, Alexandre Levine
wrote:
Hey M Ranga Swami Reddy (sorry, I'm not sure how to address you shorter :)
),
After conversation in this mailing list with Michael Still I understood that
I'll do the sub group and meetings stuff, since I lead the ec2-api in
stackforge anyways. Of course I
Yaroslav,
The bug:
https://bugs.launchpad.net/nova/+bug/1410622
And the review:
https://review.openstack.org/#/c/152112/
It's recently fixed.
Best regards,
Alex Levine
On 2/11/15 2:23 PM, Yaroslav Lobankov wrote:
Hello everyone,
I have some question about EC2 Tempest tests. When I run the
ot;
attrs_to_use.extends(array_of_new_stuff)
I think we support api_version decorator, see
https://review.openstack.org/141983
But we need add decorator in the servers' index/detail and also in
this extend method.
for attr in ['host', 'name']:
All,
I have updated and reworked the review with the proposed microversions
changes. Please take a look.
Hope tomorrow during the nova meeting we'll decide something about it.
Best regards,
Alex Levine
On 2/17/15 5:54 PM, Sean Dague wrote:
On 02/17/2015 09:38 AM, Alexandre Levine
All,
We've finished setting up the functional testing for the stackforge EC2
API project. New test suite consists of 96 API and scenario tests
covering almost (tags functionality and client tokens absent) all of the
functionality initially covered by original EC2 API tests in Tempest and
much
Bump.
I'd really appreciate some answers to the question Sean asked. I still
have the 2.4 in my review (the very one Sean mentioned) but it seems
that it might not be the case.
Best regards,
Alex Levine
On 3/2/15 2:30 PM, Sean Dague wrote:
This change for the additional attributes for ec2
ange which uses
microversions https://review.openstack.org/#/c/140313/ can merge (has
3 +2's just needs the v2.1 fix first.
________
From: Alexandre Levine [alev...@cloudscaling.com]
Sent: Tuesday, March 03, 2015 4:22 PM
To: OpenStack Development Mailing Li
od
enough? Say, all trailing changes existing now at the moment to be
packed into one microversion? I understand there are 3 of them and all
of them are ready and waiting, aren't they?
Best regards,
Alex Levine
On 3/5/15 2:53 AM, Christopher Yeoh wrote:
On Wed, Mar 4, 2015 at 9:51
Hello everyone,
We've decided to cut our first release of the standalone EC2-API
project. All of the known to us major problems are solved - NovaDB
direct access is cut off, performance is checked and improved, all of
the necessary functional, unit and Rally tests are in place.
One known cavea
56 matches
Mail list logo
