merget
env and move all files and add them into deployment plan enviroments.
https://review.openstack.org/#/c/599559/
What do you think about each of solution?Which solution should be used
in TripleO?
Best,
Kamil Sambor
[0] https://bugs.launchpad.net/tripleo/+bug/1716391
[1] https
.
Also we discuss 4th solution, simply we should inform users about
deprecation of client and encourage users to use fuel_v2 client with new
commands and parameters.
Best regards,
Kamil Sambor
On Wed, Mar 4, 2015 at 9:28 AM, Przemyslaw Kaminski pkamin...@mirantis.com
wrote:
Maybe add a Changelog
to switch to
new client and it will be easy for us to migrate only old commands. Now
when we add new command we add to old client and then in future still need
to migrate it. SO keeping two entry points for fuel-client IMHO will
be convenient for developers and for users.
Best regards,
Kamil Sambor
Thank you guys for response.
There is no cons, so we migrate validation to separate repo.
Best regards,
Kamil Sambor
On Wed, Feb 18, 2015 at 9:34 AM, Evgeniy L e...@mirantis.com wrote:
+1 to extract validators for granular deployment tasks
Dmitry, do you mean that we should create some cli
mocks if it is
necessary. If we will have test run on nailgun we can be sure that even if
responses has been changed, client can still work or when we add new API
our client realy works with API, not only with mocked responses.
Best regards,
Kamil Sambor
On Mon, Feb 9, 2015 at 1:57 PM, Nikolay
Tomasz we are not using ssl in our client so now we not gain anything from
moving to 2.7 .
Best regards,
– Kamil S.
On Wed, Jan 14, 2015 at 8:32 AM, Bartłomiej Piotrowski
bpiotrow...@mirantis.com wrote:
On 01/13/2015 11:16 PM, Tomasz Napierala wrote:
On 13 Jan 2015, at 10:51, Przemyslaw
Additionaly to what Przemek wrote, also Pecan is released more often, IMHO
documentation is better written, and described a lot of possibilities of
modification, also as Lukasz wrote in previous thread that Pecan is used in
openstack.
So I'm also for Pecan
Best regards,
Kamil S.
On Wed, Dec 3,
Hi folks,
All parts of code related to stage I and II from blueprint
http://docs-draft.openstack.org/29/96429/11/gate/gate-fuel-specs-docs/2807f30/doc/build/html/specs/5.1/access-control-master-node.htm
