Re: [openstack-dev] [Glance][All] Pecan migration strategies

2014-01-14 Thread Roman Prykhodchenko
should be as painless as possible. Regards, Roman Prykhodchenko On Jan 10, 2014, at 14:51 , Flavio Percoco fla...@redhat.com wrote: Greetings, More discussions around the adoption of Pecan. I'd like to know what is the feeling of other folks about migrating existing APIs to Pecan

Re: [openstack-dev] [Ironic] review days

2014-02-12 Thread Roman Prykhodchenko
I think that's a nice idea. During the last two days using this approach we managed to find several problems in an important patch which is now waiting to be merged. I bet it would take much longer, if we didn't do that. How about picking a particular time every day for performing this kind of

Re: [openstack-dev] [Ironic] review days

2014-02-12 Thread Roman Prykhodchenko
Since there are two core-subteams located in different time zones I propose making two sessions: - One in the morning in Europe. Let's say at 10 GMT - One in the morning in the US at a convenient time. This approach might be useful for the submitters located in different time zones. -

Re: [openstack-dev] [Ironic] review days

2014-02-13 Thread Roman Prykhodchenko
8am PST mostly works for me (except Wednesdays ), so +1 to that. - romcheg On Feb 13, 2014, at 09:44 , Ghe Rivero ghe.riv...@gmail.com wrote: What time would work for you? How about Thursdays at 8am PST? Works for me! Ghe Rivero ___

Re: [openstack-dev] [Ironic] Nominating Lucas Gomes to ironic core

2013-10-25 Thread Roman Prykhodchenko
Totally agree. On Oct 25, 2013, at 03:18 , Devananda van der Veen devananda@gmail.com wrote: Hi all, I'd like to nominate Lucas Gomes for ironic-core. He's been consistently doing reviews for several months and has led a lot of the effort on the API and client libraries. Thanks

Re: [openstack-dev] Revisiting current column number limit in code

2013-10-30 Thread Roman Prykhodchenko
Hi there, Limiting the lines to 80 symbols makes viewing/editing/comparing two files on a single screen quite comfortable. This is not only useful for Vimers who do not use graphical IDEs but also makes debugging/troubleshooting easier when someone has a development/preproduction server(s)

[openstack-dev] [Hacking] License headers in empty files

2013-11-28 Thread Roman Prykhodchenko
Hi folks, according to our hacking rules all source files should contain the Apache license header in the beginning (http://docs.openstack.org/developer/hacking/#openstack-licensing). There are special files that in most of the cases are empty, i.e., __init__.py. I used to put license headers

Re: [openstack-dev] [Hacking] License headers in empty files

2013-11-28 Thread Roman Prykhodchenko
s...@dague.net wrote: On 11/28/2013 01:01 PM, Julien Danjou wrote: On Thu, Nov 28 2013, Roman Prykhodchenko wrote: The point of this email is _not_ to blame someone or to push my personal opinion to the folks who gave me the feedback. What I'm trying to do is to to bring more clarity to our

[openstack-dev] [policy] Let's make topics mandatory for openstack-dev

2013-12-05 Thread Roman Prykhodchenko
of emails in openstack-dev do not contain topics in their subjects, which makes this kind of filtering very ineffective. My proposal is to create an automated rule that rejects new emails, if they do not contain any topic in their subject. What do you guys think? - Roman Prykhodchenko - romcheg

Re: [openstack-dev] [policy] Let's make topics mandatory for openstack-dev

2013-12-05 Thread Roman Prykhodchenko
December 2013 22:35, Roman Prykhodchenko rprikhodche...@mirantis.com wrote: Hi folks, My proposal is to create an automated rule that rejects new emails, if they do not contain any topic in their subject. What do you guys think? My expectation is that [ALL] would be the result, for things

Re: [openstack-dev] [Ironic] proposal to remove Roman Prykhodchenko from the core team

2014-07-12 Thread Roman Prykhodchenko
That is true, last month my work on Ironic is about interacting with different third party stuff (migration, testing, etc.) that required more attention than Ironic itself. I will continue working on making Ironic better independent on my status in Gerrit (just as I did before I was a

Re: [openstack-dev] [Ironic] proposal to remove Roman Prykhodchenko from the core team

2014-07-12 Thread Roman Prykhodchenko
It’s a stupid typo but it changes the sense of my last email; Of course I mean months, not month. On Jul 12, 2014, at 14:06, Roman Prykhodchenko rprikhodche...@mirantis.com wrote: That is true, last month my work on Ironic is about interacting with different third party stuff (migration

Re: [openstack-dev] [Ironic] Nominating Jim Rollenhagen to ironic-core

2014-07-14 Thread Roman Prykhodchenko
A big +1 from me too! Jim's doing a great job in Ironic team. On Mon, Jul 14, 2014 at 6:24 AM, Haomeng, Wang wanghaom...@gmail.com wrote: +1:) On Sun, Jul 13, 2014 at 3:00 AM, Lucas Alvares Gomes lucasago...@gmail.com wrote: +1 ! On Fri, Jul 11, 2014 at 11:50 PM, Devananda van der

Re: [openstack-dev] [Ironic] Nominating David Shrewsbury to ironic-core

2014-07-14 Thread Roman Prykhodchenko
+1! On Mon, Jul 14, 2014 at 6:24 AM, Haomeng, Wang wanghaom...@gmail.com wrote: +1:) On Sun, Jul 13, 2014 at 2:59 AM, Lucas Alvares Gomes lucasago...@gmail.com wrote: +1 ! On Fri, Jul 11, 2014 at 11:50 PM, Devananda van der Veen devananda@gmail.com wrote: Hi all! While

Re: [openstack-dev] [Ironic] Proposal for slight change in our spec process

2014-08-05 Thread Roman Prykhodchenko
Hi! I think this is a nice idea indeed. Do you plan to use this process starting from Juno or as soon as possible? - Roman On Aug 5, 2014, at 22:33, Devananda van der Veen devananda@gmail.com wrote: Hi all! The following idea came out of last week's midcycle for how to improve our

Re: [openstack-dev] [Ironic] March core team review

2014-04-08 Thread Roman Prykhodchenko
+1 for those guys. On Tue, Apr 8, 2014 at 6:35 PM, Lucas Alvares Gomes lucasago...@gmail.comwrote: So, I'd like to formally propose that Ruby (rloo), Haomeng (whaom), and Yuriy (yuriyz) be added to the core team at this time. I believe they have all been very helpful over the last few

Re: [openstack-dev] [Ironic] detailed git commit messages

2014-04-28 Thread Roman Prykhodchenko
That seems to be reasonable to me. Perhaps we should define a more or less formal format for commit messages? That might both help newcomers to write them make it easier for us to write sensible What's changed documents basing on those commit messages. - Roman On пн, 28-кві-2014 14:41:58

Re: [openstack-dev] [Ironic] A mascot for Ironic

2014-11-17 Thread Roman Prykhodchenko
Bear Metal +1 On 17 Nov 2014, at 12:00, Lucas Alvares Gomes lucasago...@gmail.com wrote: I'm adding all the names suggestions to the Ironic WhiteBoard etherpad[1] (at the bottom). Feel free to include more names there and then we can call a vote. [1]

[openstack-dev] [FUEL]Re-thinking Fuel Client

2014-11-17 Thread Roman Prykhodchenko
Hi folks! I’ve made several internal discussions with Łukasz Oleś and Igor Kalnitsky and decided that the existing Fuel Client has to be redesigned. The implementation of the client we have at the moment does not seem to be compliant with most of the use cases people have in production and

Re: [openstack-dev] [FUEL]Re-thinking Fuel Client

2014-11-20 Thread Roman Prykhodchenko
On Mon, Nov 17, 2014 at 8:08 PM, Roman Prykhodchenko rprikhodche...@mirantis.com mailto:rprikhodche...@mirantis.com wrote: Hi folks! I’ve made several internal discussions with Łukasz Oleś and Igor Kalnitsky and decided that the existing Fuel Client has to be redesigned. The implementation

Re: [openstack-dev] [FUEL]Re-thinking Fuel Client

2014-11-20 Thread Roman Prykhodchenko
Dean, thank you for your input. On 20 Nov 2014, at 15:43, Dean Troyer dtro...@gmail.com wrote: [pardon my jumping in like kibo, someone mentioned 'client' ;) ] Now I know for sure how to summon you :) On Thu, Nov 20, 2014 at 3:01 AM, Vladimir Kozhukalov vkozhuka...@mirantis.com

[openstack-dev] [Fuel][Nailgun]Problems with auto-reloading

2014-12-02 Thread Roman Prykhodchenko
Hi folks, today we encountered a problem caused by auto-reload feature and our code-organisation. The problem is that web.py tries reloading modules at some point and while it does that it expects that modules could be reloaded in any order without raising any errors. Unfortunately for

Re: [openstack-dev] Add IDE specific directories to .gitignore

2013-06-18 Thread Roman Prykhodchenko
Chmouel, Yes, it's possible to set up excluded directories in several ways. My question was why not make those directories excluded by default? - Roman On Jun 18, 2013, at 11:14 , Chmouel Boudjnah chmo...@enovance.com wrote: On Tue, Jun 18, 2013 at 9:50 AM, Roman Prykhodchenko rprikhodche

[openstack-dev] [ironic] Legal issue with the name Ironic

2013-06-19 Thread Roman Prykhodchenko
Hi folks! Recently was trying to Google the launchpad page of Ironic project and found a company named Ironic Software (http://www.ironicsoftware.com). I'm not a lawyer but I think we might experience legal issues unless we give Ironic a different name. - Roman Prykhodchenko

Re: [openstack-dev] [Ironic] Nomination to add Chris Krelle to ironic core

2013-07-31 Thread Roman Prykhodchenko
+1 Chris is doing great job for Ironic. On Jul 31, 2013, at 19:20 , Ghe Rivero g...@debian.org wrote: +1 On Wed, Jul 31, 2013 at 6:10 PM, Devananda van der Veen devananda@gmail.com wrote: Hi, I'd like to propose to add Chris (NobodyCam) to ironic-core. He has been doing a lot

Re: [openstack-dev] [CI] Now gating on Python 3.3

2013-08-01 Thread Roman Prykhodchenko
Jeremy, thank you for this announce. It would be very helpful to mention those projects. - Roman Prykhodchenko On Aug 1, 2013, at 06:18 , Jeremy Stanley fu...@yuggoth.org wrote: A quick announcement... thanks to the invaluable assistance of Chuck Short, Dan Prince, Julien Danjou and others

[openstack-dev] [devstack] Review request for 41053

2013-09-02 Thread Roman Prykhodchenko
Hi fellows, Can someone of the devstack-core team please review this patch: https://review.openstack.org/#/c/41053/ ? - Roman ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org

Re: [openstack-dev] [Fuel][Nailgun] Web framework

2014-12-03 Thread Roman Prykhodchenko
I don’t have an opinion for now but do have some thoughts instead. We use Pecan in Ironic. I could say that it’s pretty nice when one needs to make something simple but requires some manual job to be done in more or less sophisticated cases. On the other hand we have that the Pecan team is quire

Re: [openstack-dev] [Fuel][Nailgun] Web framework

2014-12-03 Thread Roman Prykhodchenko
Being able to make some impact on Pecan is an advantage for sure. But there are other aspects in choosing a web framework and I’d rather discuss them. Let’s not think about what is used in other OpenStack projects for a moment and discuss technical details. On 03 Dec 2014, at 15:53, Jay Pipes

Re: [openstack-dev] [Fuel][Nailgun] Web framework

2014-12-04 Thread Roman Prykhodchenko
I’d rather suggest doing in several iteration by replacing several resources by Pecan’s implementations. Doing that in one big patch-set will make reviewing very painful, so some bad things might be not noticed. On 04 Dec 2014, at 14:01, Igor Kalnitsky ikalnit...@mirantis.com wrote: Ok,

Re: [openstack-dev] [Ironic] Fuel agent proposal

2014-12-09 Thread Roman Prykhodchenko
It is true that IPA and FuelAgent share a lot of functionality in common. However there is a major difference between them which is that they are intended to be used to solve a different problem. IPA is a solution for provision-use-destroy-use_by_different_user use-case and is really great for

Re: [openstack-dev] [Fuel] Logs format on UI (High/6.0)

2014-12-15 Thread Roman Prykhodchenko
Hi folks! In most productions environments I’ve seen bare logs as they are shown now in Fuel web UI were pretty useless. If someone has an infrastructure that consists of more that 5 servers and 5 services running on them they are most likely to use logstash, loggly or any other log management

Re: [openstack-dev] [Fuel] Core rights in Fuel repositories

2015-01-24 Thread Roman Prykhodchenko
Of course I mean program-release and program-milestone. 24 січ. 2015 о 02:37 Roman Prykhodchenko m...@romcheg.me написав(ла): Aleksandra, a general practice is to have program-core and program-milestone groups. That approach fits for fuel-* as well because there’s only one separate team

Re: [openstack-dev] [Fuel][client][IMPORTANT] Making Fuel Client a separate project

2015-01-26 Thread Roman Prykhodchenko
+status:open+file:%255Efuelclient/.*,n,z [3] https://review.openstack.org/#/c/149797/ - romcheg 16 січ. 2015 о 17:13 Roman Prykhodchenko m...@romcheg.me написав(ла): Hi Fuelers, this is another status update. - OpenStack-CI is now running pep8 checks [1] for patches to python-fuelclient

Re: [openstack-dev] [Fuel][Agent] Moving Fuel Agent to a separate repo

2015-01-26 Thread Roman Prykhodchenko
Vladimir, As a fuel-separatist I give this initiative a big +1 because of the following advantages I can see: - Git is designed for keeping smaller single-compoent repos, keeping everything to one repo is a discouraged pattern - Having a separate -core group that will only contain active

Re: [openstack-dev] [fuel][client] new client implementation ideas

2015-01-16 Thread Roman Prykhodchenko
Konstantin, thank you for your ideas, I think we will definitely want to use something like that. Lets discuss some nits in the etherpad you’ve created. - romcheg 16 січ. 2015 о 13:03 Konstantin Danilov kdani...@mirantis.com написав(ла): Hi all, I have created etherpad page

Re: [openstack-dev] [Fuel][client][IMPORTANT] Making Fuel Client a separate project

2015-01-16 Thread Roman Prykhodchenko
verify-python-fuelclient https://review.fuel-infra.org/#/c/1989 https://review.fuel-infra.org/#/c/1989 - romcheg 13 січ. 2015 о 15:58 Roman Prykhodchenko m...@romcheg.me написав(ла): Folks, this is another status update. The patch for moving python-fuelclient to a separate project has

[openstack-dev] [Fuel][client] Keeping Nailgun's log after running tests

2015-01-19 Thread Roman Prykhodchenko
Hi folks, at the moment run_test.sh script removes Nailgun's log file after running. The question is whether it is necessary to add an option for keeping it. - romcheg signature.asc Description: Message signed with OpenPGP using GPGMail

Re: [openstack-dev] [Fuel] Proposal for nominating people to python-fuelclient-core

2015-01-27 Thread Roman Prykhodchenko
I think the consensus was found and the resolution is positive. 26 січ. 2015 о 14:37 Tomasz Napierala tnapier...@mirantis.com написав(ла): +1 On 26 Jan 2015, at 11:33, Roman Prykhodchenko m...@romcheg.me wrote: Hi Guys, According to our previous thread [1] and the decision made

Re: [openstack-dev] [Fuel] Core rights in Fuel repositories

2015-01-26 Thread Roman Prykhodchenko
24 січ. 2015 о 21:39 Roman Prykhodchenko m...@romcheg.me написав(ла): Of course I mean program-release and program-milestone. 24 січ. 2015 о 02:37 Roman Prykhodchenko m...@romcheg.me написав(ла): Aleksandra, a general practice is to have program-core and program-milestone groups

[openstack-dev] [Fuel] Proposal for nominating people to python-fuelclient-core

2015-01-26 Thread Roman Prykhodchenko
Hi Guys, According to our previous thread [1] and the decision made there I’d like to initiate separation of the original fuel-core group. At the first step propose the following python guys from the original fuel-core group to be nominated to python-fuelclient-core group. Aleksey Kasatkin —

Re: [openstack-dev] [Fuel] Core rights in Fuel repositories

2015-01-23 Thread Roman Prykhodchenko
group for all repositories or every repository needs its own? On Fri, Jan 23, 2015 at 7:04 PM, Roman Prykhodchenko m...@romcheg.me wrote: Hi folks! After moving python-fuelclient to its own repo some of you started asking a good question which is How do we manage core rights in different

Re: [openstack-dev] [Fuel][Agent] Moving Fuel Agent to a separate repo

2015-01-26 Thread Roman Prykhodchenko
now, as we use git hashes, and not fixed versions, or packages. Maybe we should complete the python-fuelclient transformation first and see how it is going to work for us? On Jan 26, 2015 8:59 PM, Roman Prykhodchenko m...@romcheg.me wrote: Vladimir, As a fuel-separatist I give

[openstack-dev] [Fuel] Dropping Python-2.6 support

2015-01-12 Thread Roman Prykhodchenko
Folks, as it was planned and then announced at the OpenStack summit OpenStack services deprecated Python-2.6 support. At the moment several services and libraries are already only compatible with Python=2.7. And there is no common sense in trying to get back compatibility with Py2.6 because

Re: [openstack-dev] [Fuel][client][IMPORTANT] Making Fuel Client a separate project

2015-01-12 Thread Roman Prykhodchenko
://bugs.launchpad.net/fuel/+bug/1409673 https://bugs.launchpad.net/fuel/+bug/1409673 python-fuelclient on PyPi https://pypi.python.org/pypi/python-fuelclient https://pypi.python.org/pypi/python-fuelclient 9 січ. 2015 о 15:14 Roman Prykhodchenko m...@romcheg.me mailto:m...@romcheg.me написав(ла

Re: [openstack-dev] [Fuel][client][IMPORTANT] Making Fuel Client a separate project

2015-01-13 Thread Roman Prykhodchenko
testing process in FuelCI, testing in OpenStack CI will be enabled later because that requires some refactoring of the existing tests in python-fuelclient. Stay tuned. - romcheg 12 січ. 2015 о 12:44 Roman Prykhodchenko m...@romcheg.me написав(ла): Hi folks! This is a status update

[openstack-dev] [Fuel][client][IMPORTANT] Making Fuel Client a separate project

2015-01-09 Thread Roman Prykhodchenko
Hi folks, according to the Fuel client refactoring plan [1] it’s necessary to move it out to a separate repository on Stackforge. The process of doing that consists of two major steps: - Landing a patch [2] to project-config for creating a new Stackforge project - Creating an initial core group

Re: [openstack-dev] [Fuel] fuel-client and Nailgun API

2015-02-09 Thread Roman Prykhodchenko
Actually it was not a hollywar but a small discussion which get no continuation due to low priority and some technical problems. The point is that ATM unit tests in python-fuelclient act like integration tests because they require a live instance of the Nailgun API and certain data in

[openstack-dev] [Fuel] Let's stick to OpenStack global requirements

2015-03-18 Thread Roman Prykhodchenko
Hi folks, before you say «romcheg, go away and never come back again!», please read the story that caused me to propose this and the proposed solution. Perhaps it makes you reconsider :) As you know for different reasons, among which are being able to set up everything online and bringing

[openstack-dev] [Fuel] FFE python-fuelclient improvements

2015-03-16 Thread Roman Prykhodchenko
Hi folks, due to some technical issues we were unable to merge Cliff integration patches to keep ISO build jobs alive. Since now the problem is fixed and we are unblocked, I’d like to ask for a FFE in order to merge that all. - romcheg signature.asc Description: Message signed with OpenPGP

Re: [openstack-dev] [Fuel] FFE python-fuelclient improvements

2015-03-19 Thread Roman Prykhodchenko
at 12:50 PM, Evgeniy L e...@mirantis.com mailto:e...@mirantis.com wrote: +1, because those patches are simple don't look destructive. On Mon, Mar 16, 2015 at 7:43 PM, Roman Prykhodchenko m...@romcheg.me mailto:m...@romcheg.me wrote: Hi folks, due to some technical issues we were

Re: [openstack-dev] [Fuel] Let's stick to OpenStack global requirements

2015-03-19 Thread Roman Prykhodchenko
) to split those repositories. How this workflow will work with those separated repos? Will we still need it? Thanks! Sebastian 2015-03-18 11:04 GMT+01:00 Roman Prykhodchenko m...@romcheg.me: Hi folks, before you say «romcheg, go away and never come back again!», please read the story

Re: [openstack-dev] [Fuel] Deprecation warnings in python-fuelclient-6.1.*

2015-03-06 Thread Roman Prykhodchenko
-client IMHO will be convenient for developers and for users. Best regards, Kamil Sambor On Wed, Mar 4, 2015 at 10:54 AM, Roman Prykhodchenko m...@romcheg.me wrote: I’d like to resolve some questions: @Przemysław: - We can avoid that message by supplying --quiet. - Changelog

[openstack-dev] [Fuel] Version bump in the beginning of a release cycle

2015-03-26 Thread Roman Prykhodchenko
Hi folks, This end of the release cycle I realized that due to different reasons bumping a version of Fuel’s components takes much more than just updating a set of text files. In fact it causes different kinds of cross-component problems which of course must be fixed. This email is not about

Re: [openstack-dev] [Fuel] Let's stick to OpenStack global requirements

2015-03-26 Thread Roman Prykhodchenko
:16 PM, Roman Prykhodchenko m...@romcheg.me wrote: Folks, I assume you meant: If a requirement that previously was only in Fuel Requirements is merged to Global Requirements, it should be removed from *Fuel* Requirements». Exactly. I'm not sure it's good idea. We should stay so close

Re: [openstack-dev] [Fuel] Let's stick to OpenStack global requirements

2015-04-01 Thread Roman Prykhodchenko
partially fixes this issue. The only thing I’d like to add to that scheme is this: - Add a CI jod that on daily basis checks whether python-requirements are in line with the requirements in RPM specs. - romcheg 26 бер. 2015 о 12:07 Roman Prykhodchenko m...@romcheg.me написав(ла): So guys, I

Re: [openstack-dev] [Fuel] fuel-dev-tools repo

2015-03-27 Thread Roman Prykhodchenko
IIRC in this thread we agreed to use separate core groups for different repositories http://lists.openstack.org/pipermail/openstack-dev/2015-January/055111.html http://lists.openstack.org/pipermail/openstack-dev/2015-January/055111.html Why not follow that approach in this case? 27 бер. 2015

Re: [openstack-dev] [Fuel] Deprecation warnings in python-fuelclient-6.1.*

2015-03-04 Thread Roman Prykhodchenko
, it is not very disturbing and shouldn't break any currently used automation scripts. P. On 03/03/2015 03:52 PM, Roman Prykhodchenko wrote: Hi folks! According to the refactoring plan [1] we are going to release the 6.1 version of python-fuelclient which is going to contain recent

[openstack-dev] [Fuel] Deprecation warnings in python-fuelclient-6.1.*

2015-03-03 Thread Roman Prykhodchenko
Hi folks! According to the refactoring plan [1] we are going to release the 6.1 version of python-fuelclient which is going to contain recent changes but will keep backwards compatibility with what was before. However, the next major release will bring users the fresh CLI that won’t be

[openstack-dev] [Fuel] Core rights in Fuel repositories

2015-01-23 Thread Roman Prykhodchenko
Hi folks! After moving python-fuelclient to its own repo some of you started asking a good question which is How do we manage core rights in different Fuel repositories. The problem is that there is a single fuel-core group which is used for all fuel-* repos, except for python-fuelclient. The

[openstack-dev] [Fuel] Transaction scheme

2015-04-30 Thread Roman Prykhodchenko
Hi folks! Recently I faced a pretty sad fact that in Nailgun there’s no common approach to manage transactions. There are commits and flushes in random places of the code and it used to work somehow just because it was all synchronous. However, after just a few of the subcomponents have been

[openstack-dev] [Fuel] python-fuelclient 6.1.0 is released

2015-05-15 Thread Roman Prykhodchenko
Hi folks! I’m glad to announce that the first independent release of Fuel Client was published to PyPi: https://pypi.python.org/pypi/python-fuelclient https://pypi.python.org/pypi/python-fuelclient You can either download it from the web page or install with pip install python-fuelclient.

Re: [openstack-dev] [Fuel] PEP8 issues in Fuel-Web repo

2015-04-07 Thread Roman Prykhodchenko
This is also relevant for python-fuelclient. 6 квіт. 2015 о 12:27 Nikolay Markov nmar...@mirantis.com написав(ла): Hello everyone, I know this is really low priority and so on, but here is this bug about moving to the newest version of hacking package:

Re: [openstack-dev] [Fuel] Improvement of the blueprint specs template

2015-06-18 Thread Roman Prykhodchenko
I realize, that discussing this topic in the email is hard. I filed a review request with some changes to the template and invite you folks to take a look at that: https://review.openstack.org/193070 https://review.openstack.org/193070 16 черв. 2015 о 17:08 Roman Prykhodchenko m

Re: [openstack-dev] [Fuel] Improvement of the blueprint specs template

2015-06-19 Thread Roman Prykhodchenko
Guys, I’d like to ask all Fuel component leads to take a look at the proposed changes and check whether all important sections were added. - romcheg 18 черв. 2015 о 13:14 Roman Prykhodchenko m...@romcheg.me написав(ла): I realize, that discussing this topic in the email is hard. I filed

[openstack-dev] [Fuel] Improvement of the blueprint specs template

2015-06-16 Thread Roman Prykhodchenko
Hi folks! I was reviewing one of specs for Fuel 7.0 and realized the information there is messed up and it’s pretty hard to put it all together. The reason for that is basically that Fuel is a multicomponent project but the template does not consider that — there is a Proposed change section

Re: [openstack-dev] [Fuel] Setting cluster status when provisioning a node

2015-05-27 Thread Roman Prykhodchenko
then an element of data model? Or that's exactly the complexity you want to get rid of? -- Best regards, Oleg Gelbukh On Tue, May 26, 2015 at 4:16 PM, Roman Prykhodchenko m...@romcheg.me mailto:m...@romcheg.me wrote: Oleg, Aleksander also proposed a nice proposed a nice solution [1

[openstack-dev] [Fuel] python-fuelclient-6.1.2

2015-07-02 Thread Roman Prykhodchenko
Folks, I’m glad to announse that verison 6.1.2 of Fuel Client was released. The team fixed a few important issues in order to make it possible to interact with Fuel 6.1 using the official client. CHANGELOG === 6.1.2 --- * Change version to 6.1.2 * Update link to developers'

Re: [openstack-dev] [Fuel] python-fuelclient 6.1.0 is released

2015-05-25 Thread Roman Prykhodchenko
. Could you please elaborate on backwards compatibility between the new client and older versions of Fuel API? For example, is it possible to use the new client to work with Fuel 4.x? 5.x? -- Best regards, Oleg Gelbukh On Fri, May 15, 2015 at 5:39 PM, Roman Prykhodchenko m...@romcheg.me

Re: [openstack-dev] [Fuel] Setting cluster status when provisioning a node

2015-05-26 Thread Roman Prykhodchenko
will implement it. Aleksey Kasatkin On Fri, May 22, 2015 at 5:33 PM, Roman Prykhodchenko m...@romcheg.me mailto:m...@romcheg.me wrote: Hi folks! Recently I encountered an issue [1] that the Deploy Changes button in the web ui is still active when a provisioning of single node

Re: [openstack-dev] [Fuel] Setting cluster status when provisioning a node

2015-05-26 Thread Roman Prykhodchenko
, it would be enough if environment was set to 'operational' when all nodes in it become 'ready', no matter how they were deployed (i.e. via Web UI or CLI). -- Best regards, Oleg Gelbukh On Fri, May 22, 2015 at 5:33 PM, Roman Prykhodchenko m...@romcheg.me mailto:m...@romcheg.me wrote: Hi

[openstack-dev] [Fuel] Setting cluster status when provisioning a node

2015-05-23 Thread Roman Prykhodchenko
Hi folks! Recently I encountered an issue [1] that the Deploy Changes button in the web ui is still active when a provisioning of single node is started using the command line client. The background for that issue is that the provisioning task does not seem to update the cluster status

[openstack-dev] [Fuel] Setting cluster status when provisioning a node

2015-05-22 Thread Roman Prykhodchenko
Hi folks! Recently I encountered an issue [1] that the Deploy Changes button in the web ui is still active when a provisioning of single node is started using the command line client. The background for that issue is that the provisioning task does not seem to update the cluster status

[openstack-dev] [Fuel] Get rid of run_test.sh in Fuel Client

2015-08-17 Thread Roman Prykhodchenko
Hi Fuelers! I was working on enabling Python tests in Fuel Client to run on OpenStack CI and I figured out that we actually have a piece of legacy code which can be removed now. That piece is run_tests.sh file. For those who’s not aware, that script allows to run different tests under

[openstack-dev] [Fuel] Great updates to tests and CI jobs

2015-08-19 Thread Roman Prykhodchenko
Hi folks! Today I’m proud to announce that since this moment python-fuelclient has it’s own python-jobs in OpenStack CI. Thanks to all of you who helped me making Fuel Client compatible with the upstream CI. Besides sharing great news I think it’s necessary to share changes we had to do, in

[openstack-dev] [Fuel] Changes to the blueprint specification template

2015-08-20 Thread Roman Prykhodchenko
Folks, as you may remember, we were about to merge some changes to the blueprint spec template to make our specifications in Fuel more specific regarding different components and subsystems. That time we decided to move the changes to 8.0, so new specs in 8.0 will have to follow the new

Re: [openstack-dev] [Fuel] Great updates to tests and CI jobs

2015-08-20 Thread Roman Prykhodchenko
On Wed, Aug 19, 2015 at 8:38 AM, Roman Prykhodchenko m...@romcheg.me mailto:m...@romcheg.me wrote: Hi folks! Today I’m proud to announce that since this moment python-fuelclient has it’s own python-jobs in OpenStack CI. Thanks to all of you who helped me making Fuel Client compatible

Re: [openstack-dev] [Fuel] Great updates to tests and CI jobs

2015-08-20 Thread Roman Prykhodchenko
all the code that uses six library for Python 2 3 compatibility. Best, Sebastian 2015-08-19 19:00 GMT+02:00 Boris Pavlovic bpavlo...@mirantis.com mailto:bpavlo...@mirantis.com: Roman, well done! ;) Best regards, Boris Pavlovic On Wed, Aug 19, 2015 at 8:38 AM, Roman

[openstack-dev] [Fuel] fuel-dev-tools package is not published on PyPi

2015-08-24 Thread Roman Prykhodchenko
Folks, I can see fuel-dev-tools packaged registered on PyPi [1] but when I tried to install it, I got a message that pip could not find a version that satisfies the requirement. These utils are extremely useful and really help to avoid much pain while testing something on a live environment

Re: [openstack-dev] [Fuel] Great updates to tests and CI jobs

2015-08-24 Thread Roman Prykhodchenko
...@mirantis.com написав(ла): If there will be 4-5 patches, then I do not have anything against it. I'm just skeptic that we will have so many ;) 2015-08-20 14:05 GMT+02:00 Roman Prykhodchenko m...@romcheg.me mailto:m...@romcheg.me: I think, that if there are 4-5 patches that pass python jobs

Re: [openstack-dev] [Fuel] Release of python-fuelclient today

2015-07-31 Thread Roman Prykhodchenko
Привет, нет, обычный how to contribute. 31 лип. 2015 о 15:01 Roman Prykhodchenko m...@romcheg.me написав(ла): Folks, today I’m going to make a new public release of Fuel Client. If you badly need to merge something before that or have any objections, please let me know before 17:00 CEST

Re: [openstack-dev] [Fuel] Release of python-fuelclient today

2015-07-31 Thread Roman Prykhodchenko
Sorry, folks, I pressed a wrong button for replying. 31 лип. 2015 о 15:56 Roman Prykhodchenko m...@romcheg.me написав(ла): Привет, нет, обычный how to contribute. 31 лип. 2015 о 15:01 Roman Prykhodchenko m...@romcheg.me написав(ла): Folks, today I’m going to make a new public release

[openstack-dev] [Fuel] Release of python-fuelclient today

2015-07-31 Thread Roman Prykhodchenko
Folks, today I’m going to make a new public release of Fuel Client. If you badly need to merge something before that or have any objections, please let me know before 17:00 CEST (UTC+2). - romcheg signature.asc Description: Message signed with OpenPGP using GPGMail

Re: [openstack-dev] [fuel] [FFE] FF Exception request for Custom node attributes feature

2015-07-24 Thread Roman Prykhodchenko
+1 to merging the CLI part, if all our comments there are filed as High priority bugs and then fixed ASAP - romcheg 24 лип. 2015 о 07:58 Mike Scherbakov mscherba...@mirantis.com написав(ла): Colleagues, it sounds like we need to complete what was requested by Julia here (and it would

[openstack-dev] [Fuel] Changing APIs and API versioning

2015-10-21 Thread Roman Prykhodchenko
Hi folks, I’d like to touch the aspect of Fuel development process that seems to be as wrong as possible. That aspect is how we change the API. The issue is that in Fuel anyone can change API at any point of time without even warning the rest of the same component’s team. Relying on this kind

[openstack-dev] [Fuel] Assigning VIPs on network config serialization

2015-10-16 Thread Roman Prykhodchenko
Hi folks! I’ve been discussing several bugs [1-3] with some folks and noticed that they share the same root cause which is that network serialization fails, if there’s not enough IP addresses in all available ranges of one of the available networks to assign them to all VIPs. There are several

Re: [openstack-dev] [Fuel] Assigning VIPs on network config serialization

2015-10-20 Thread Roman Prykhodchenko
should fail, if there's not enough VIPs or > other resources. So users fix them, and try again. > * Both Fuel UI and OSTF needs VIPs only when cluster is deployed, and > it's safe to return allocated VIPs on that stage. > > So what do you think guys? > > Thanks, > I

Re: [openstack-dev] [Fuel] Assigning VIPs on network config serialization

2015-10-21 Thread Roman Prykhodchenko
. >> >> Once again - why? I agree, perhaps it would be useful, but there's no >> strict requirement on this and we should resolve our issues >> step-by-step. See my response above. >> >> >>> No, Again, this is too late. >> >> Too lat

[openstack-dev] [Fuel] Plugins related functionality in Fuel Client

2015-10-08 Thread Roman Prykhodchenko
Folks, it’s time to speak about Fuel Plugins and the way they are managed. Currently we have some methods in Fuel Client that allow to install, remove and do some other things to plugins. Everything looks great except that functionality requires Fuel Client to be installed on a master node and

Re: [openstack-dev] [Fuel] py.test vs testrepository

2015-10-08 Thread Roman Prykhodchenko
://review.openstack.org/#/c/227895 - romcheg > 7 жовт. 2015 р. о 14:41 Roman Prykhodchenko <m...@romcheg.me> написав(ла): > > Michał, > > some comments in-line > >>> - testrepository and related components are used in OpenStack Infra >>> environment f

Re: [openstack-dev] [Fuel] Plugins related functionality in Fuel Client

2015-10-09 Thread Roman Prykhodchenko
Nailgun’s API to have a single entry point. > > I don't think that application such as Nailgun should be responsible for > proxying > requests, we solved similar problem for OSTF with adding proxy rule in Nginx. > > Thanks, > > On Fri, Oct 9, 2015 at 11:45 AM, Roman Pry

Re: [openstack-dev] [Fuel] Plugins related functionality in Fuel Client

2015-10-09 Thread Roman Prykhodchenko
ce, instead of adding it > to Nailgun. > > Thanks, > > On Fri, Oct 9, 2015 at 1:40 AM, Roman Prykhodchenko <m...@romcheg.me > <mailto:m...@romcheg.me>> wrote: > Folks, > > it’s time to speak about Fuel Plugins and the way they are managed. > > Currently

Re: [openstack-dev] [Fuel] Plugins related functionality in Fuel Client

2015-10-11 Thread Roman Prykhodchenko
Since there are already two services Fuel Client has to interact with, I filed a bug, for using service discovery: https://bugs.launchpad.net/fuel/+bug/1504471 > 9 жовт. 2015 р. о 11:25 Roman Prykhodchenko <m...@romcheg.me> написав(ла): > > In that case I would suggest to al

Re: [openstack-dev] [Fuel] py.test vs testrepository

2015-10-07 Thread Roman Prykhodchenko
components, e. g., Fuel Client, first and then try in in Nailgun. - romcheg > 7 жовт. 2015 р. о 02:06 Monty Taylor <mord...@inaugust.com> написав(ла): > > On 10/06/2015 06:01 PM, Thomas Goirand wrote: >> On 10/06/2015 01:14 PM, Yuriy Taraday wrote: >>> On Mon, Oct 5, 2015

Re: [openstack-dev] [Fuel] py.test vs testrepository

2015-10-07 Thread Roman Prykhodchenko
Yuri, sticking to global requirements and interacting deeper with OpenStack Infra are up-to-date objectives for Fuel and those are pretty much technical question. However, software development is not only solving technical tasks, it also incorporates interaction between people and other teams

Re: [openstack-dev] [Fuel] py.test vs testrepository

2015-10-07 Thread Roman Prykhodchenko
Michał, some comments in-line >> - testrepository and related components are used in OpenStack Infra >> environment for much more tasks than just running tests > > If by "more tasks" you mean parallel testing, py.test also has a > possibility to do that by pytest-xdist. As Monthy mentioned,

Re: [openstack-dev] [Fuel] py.test vs testrepository

2015-10-09 Thread Roman Prykhodchenko
https://review.openstack.org/#/c/227895/ - romcheg > 9 жовт. 2015 р. о 01:51 Roman Prykhodchenko <m...@romcheg.me> написав(ла): > > Folks, > > Since we’ve reached the consensus here I’d like to invite you to review the > patch [1] that replaces py.test with testr without making debugin

Re: [openstack-dev] [fuel] Branching strategy vs feature freeze

2015-08-25 Thread Roman Prykhodchenko
Dmitry, thank you for a well described plan. May I please ask you for a little TL;DR excerpt of what’s going to be changed, because I’m affraid some folks may get lost or may not have enough time to analyze it deeply (I actually see that happening but I won’t do fingerpointing :) ). -

[openstack-dev] [Fuel] Number of IP addresses in a public network

2015-08-31 Thread Roman Prykhodchenko
Hi folks! Recently a problem that network check does not tell whether there’s enough IP addresses in a public network [1] was reported. That check is performed by CheckBeforeDeployment task, but there is two problems that happen because this verification is done that late: - A deployment

[openstack-dev] [Fuel] python-jobs now vote on Fuel Client

2015-09-08 Thread Roman Prykhodchenko
Good news folks! Since python jobs worked well on a number of patches, their mode was switched to voting. They were also added to the gate pipeline. - romcheg signature.asc Description: Message signed with OpenPGP using GPGMail

  1   2   >