Re: [openstack-dev] Branch miss-match between server and client in Kilo

[Janki Chhatbar]

  Hi SridharThanks for looking into this. Everybody I know is using Kilo believing that it is the most stable. Even I use Kilo for all my experimentation / POC stuff. Since it is close to EOL, I don't mind shifting to Liberty/Mitika. Yes, I am a new contributor and am willing to continue with the contributions. I would definitely look into more bugs and am already in the tacker IRC channel. Hoping to talk‎ to you more at #tacker.ThanksJanki ChhatbarSent from my BlackBerry 10 smartphone.From: Sridhar RamaswamySent: Saturday, 12 March 2016 05:34To: OpenStack Development Mailing List (not for usage questions)Reply To: OpenStack Development Mailing List (not for usage questions)Subject: Re: [openstack-dev] Branch miss-match between server and client in KiloHi Janki,Thanks for reporting this issue and it is a valid one. However we need to fix up our gate tests to skip doc8 test for stable/kilo to merge your patchset. Given Kilo is close to EOL (end-of-life) would you mind switching over to use stable/liberty ? For Tacker, Kilo was one of the early release and we came a long way "cleaning up" the project over Liberty and Mitaka (which is wrapping up). Again, if you are particular about Kilo for any specific reason, let us know. We will find a way to work it out.BTW, I see you are new to OpenStack contributions - a warm welcome! We have many interesting work items that you could take up, see [1], particularly the ones with low-hanging-fruit tag. Stop by #tacker channel if you need help picking one.- Sridhar[1] https://goo.gl/S3FAOkOn Wed, Mar 9, 2016 at 8:16 PM, Janki Chhatbar  wrote:Hi AllGreetings for the day!I have noticed that while installing OpenStack Kilo using DevStack, the server components cloned are stable/kilo whereas the client components cloned are master. This leads to errors in installation or commands miss-match. For eg.In tacker, tacker git repo is stable/kilo which points to incorrect git repo URL. I have filled a  bug and proposed a patch for this (https://bugs.launchpad.net/tacker/+bug/1555130)In Magnum,magnum stable/kilo clones python-magnumclient master which leads to command mismatch (https://bugs.launchpad.net/magnum/+bug/1509273).Does this affect all other services? Does this mean that the branch needs to be changed for all the service's clients? The change will be in /devstack/lib/{service} file in "GITBRANCH" variable. If changes are required, I am willing to work on those.Thanking youJanki ChhatbarOpenStack | SDN | Docker(+91) 9409239106simplyexplainedblog.wordpress.com

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] Branch miss-match between server and client in Kilo

[Sridhar Ramaswamy]

Hi Janki,

Thanks for reporting this issue and it is a valid one. However we need to
fix up our gate tests to skip doc8 test for stable/kilo to merge your
patchset. Given Kilo is close to EOL (end-of-life) would you mind switching
over to use stable/liberty ? For Tacker, Kilo was one of the early release
and we came a long way "cleaning up" the project over Liberty and Mitaka
(which is wrapping up). Again, if you are particular about Kilo for any
specific reason, let us know. We will find a way to work it out.

BTW, I see you are new to OpenStack contributions - a warm welcome! We have
many interesting work items that you could take up, see [1], particularly
the ones with low-hanging-fruit tag. Stop by #tacker channel if you need
help picking one.

- Sridhar

[1] https://goo.gl/S3FAOk


On Wed, Mar 9, 2016 at 8:16 PM, Janki Chhatbar 
wrote:

> Hi All
>
> Greetings for the day!
>
> I have noticed that while installing* OpenStack Kilo* using DevStack, the
> server components cloned are stable/kilo whereas the client components
> cloned are master. This leads to errors in installation or commands
> miss-match. For eg.
>
> *In tacker,*
> tacker git repo is stable/kilo which points to incorrect git repo URL. I
> have filled a  bug and proposed a patch for this (
> https://bugs.launchpad.net/tacker/+bug/1555130)
>
> *In Magnum*,
> *magnum stable/kilo* clones *python-magnumclient master* which leads to
> command mismatch (https://bugs.launchpad.net/magnum/+bug/1509273).
>
>
>1. Does this affect all other services?
>2. Does this mean that the branch needs to be changed for all the
>service's clients? The change will be in /devstack/lib/{service} file in
>"GITBRANCH" variable.
>
>  If changes are required, I am willing to work on those.
>
> Thanking you
>
> Janki Chhatbar
> OpenStack | SDN | Docker
> (+91) 9409239106
> simplyexplainedblog.wordpress.com
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] Branch miss-match between server and client in Kilo

[Janki Chhatbar]

Hi Adrian

Greetings for the day! Thank you for replying. I would be glad to have you
help me out in this. Below are some of the points that I have noticed.


   1. > I think we can address this by creating a branch for the client
   that aligns with kilo.

There are  version specific branches for client. Devstack is to be
configured to point to the client's kilo branches.

To elaborate:
The *stackrc* file for Devstack Kilo (
https://github.com/openstack-dev/devstack/blob/stable/kilo/stackrc)
specifies the master branch for all client components and kilo branch for
server components.

# ceilometer client library
> GITREPO["python-ceilometerclient"]=${CEILOMETERCLIENT_REPO:-${GIT_BASE}/
> openstack/python-ceilometerclient.git}

GITBRANCH["python-ceilometerclient"]=${CEILOMETERCLIENT_BRANCH:-master} <-
> change to be done is replace "master" with "stable/kilo" for all the
> services.


For projects like Tacker and Magnum, it is to be done at
https://github.com/openstack/tacker/blob/stable/kilo/devstack/lib/tacker

# Set up default directories

> GITREPO["python-tackerclient"]=${TACKERCLIENT_REPO:-${GIT_BASE}/stackforge
> /python-tackerclient.git} <- change the URL to /openstack/
> python-tackerclient.git}
>
> GITBRANCH["python-tackerclient"]=${TACKERCLIENT_BRANCH:master} <- change
> to be done is replace "master" with "stable/kilo" for all the services.
>
> GITREPO["tacker-horizon"]=${TACKERHORIZON_REPO:-${GIT_BASE}/stackforge/
> python-tackerclient.git} <- change the URL to /openstack/
> python-tackerclient.git}



> GITBRANCH["tacker-horizon"]=${TACKERHORZION_BRANCH:-master} <- change to
> be done is replace "master" with "stable/kilo"
>

2. Kilo doesnot support "doc8" tests. (This is what I have noticed while
getting a Tacker patch (https://bugs.launchpad.net/tacker/+bug/1555130)
reviewed (https://review.openstack.org/#/c/290674/). I am not sure how to
proceed in such scenario.


Any guidance will be appreciated.

Thanking you

Janki Chhatbar
OpenStack | SDN | Docker
(+91) 9409239106
simplyexplainedblog.wordpress.com

On Fri, Mar 11, 2016 at 1:51 AM, Adrian Otto 
wrote:

> Hi there Janki. Thanks for catching that. I think we can address this by
> creating a branch for the client that aligns with kilo. I’ve triaged the
> magnum bug on this, and I’m willing to help drive it to resolution
> together.
>
> Regards,
>
> Adrian
>
> On Mar 9, 2016, at 8:16 PM, Janki Chhatbar 
> wrote:
>
> Hi All
>
> Greetings for the day!
>
> I have noticed that while installing* OpenStack Kilo* using DevStack, the
> server components cloned are stable/kilo whereas the client components
> cloned are master. This leads to errors in installation or commands
> miss-match. For eg.
>
> *In tacker,*
> tacker git repo is stable/kilo which points to incorrect git repo URL. I
> have filled a  bug and proposed a patch for this (
> https://bugs.launchpad.net/tacker/+bug/1555130)
>
> *In Magnum*,
> *magnum stable/kilo* clones *python-magnumclient master* which leads to
> command mismatch (https://bugs.launchpad.net/magnum/+bug/1509273).
>
>
>1. Does this affect all other services?
>2. Does this mean that the branch needs to be changed for all the
>service's clients? The change will be in /devstack/lib/{service} file in
>"GITBRANCH" variable.
>
>  If changes are required, I am willing to work on those.
>
> Thanking you
>
> Janki Chhatbar
> OpenStack | SDN | Docker
> (+91) 9409239106
> simplyexplainedblog.wordpress.com
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] Branch miss-match between server and client in Kilo

[Adrian Otto]

Hi there Janki. Thanks for catching that. I think we can address this by 
creating a branch for the client that aligns with kilo. I’ve triaged the magnum 
bug on this, and I’m willing to help drive it to resolution together.

Regards,

Adrian

On Mar 9, 2016, at 8:16 PM, Janki Chhatbar 
mailto:jankihchhat...@gmail.com>> wrote:

Hi All

Greetings for the day!

I have noticed that while installing OpenStack Kilo using DevStack, the server 
components cloned are stable/kilo whereas the client components cloned are 
master. This leads to errors in installation or commands miss-match. For eg.

In tacker,
tacker git repo is stable/kilo which points to incorrect git repo URL. I have 
filled a  bug and proposed a patch for this 
(https://bugs.launchpad.net/tacker/+bug/1555130)

In Magnum,
magnum stable/kilo clones python-magnumclient master which leads to command 
mismatch (https://bugs.launchpad.net/magnum/+bug/1509273).


  1.  Does this affect all other services?
  2.  Does this mean that the branch needs to be changed for all the service's 
clients? The change will be in /devstack/lib/{service} file in "GITBRANCH" 
variable.

 If changes are required, I am willing to work on those.

Thanking you

Janki Chhatbar
OpenStack | SDN | Docker
(+91) 9409239106
simplyexplainedblog.wordpress.com
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: 
openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] Branch miss-match between server and client in Kilo

[Matt Riedemann]

On 3/10/2016 9:04 AM, Matt Riedemann wrote:



On 3/9/2016 10:16 PM, Janki Chhatbar wrote:

Hi All

Greetings for the day!

I have noticed that while installing*OpenStack Kilo* using DevStack, the
server components cloned are stable/kilo whereas the client components
cloned are master. This leads to errors in installation or commands
miss-match. For eg.

_In tacker,_
tacker git repo is stable/kilo which points to incorrect git repo URL. I
have filled a  bug and proposed a patch for this
(https://bugs.launchpad.net/tacker/+bug/1555130)

_In Magnum_,
*magnum stable/kilo* clones *python-magnumclient master* which leads to
command mismatch (https://bugs.launchpad.net/magnum/+bug/1509273).

 1. Does this affect all other services?
 2. Does this mean that the branch needs to be changed for all the
service's clients? The change will be in /devstack/lib/{service}
file in "GITBRANCH" variable.

  If changes are required, I am willing to work on those.

Thanking you

Janki Chhatbar
OpenStack | SDN | Docker
(+91) 9409239106
simplyexplainedblog.wordpress.com



__

OpenStack Development Mailing List (not for usage questions)
Unsubscribe:
openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



Assuming the APIs in the server projects have not made backward
incompatible changes since Kilo, the clients from master should continue
to work. That's a big assumption with some projects, however.

If the clients on master implement CLIs for new features that landed
after Kilo, then those won't work.



By the way, normally devstack would limit the versions of the clients 
installed based on what's in global-requirements, but in your case, 
tacker and magnumclient aren't in there (they were newer after kilo):


https://github.com/openstack/requirements/blob/stable/kilo/global-requirements.txt

--

Thanks,

Matt Riedemann


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] Branch miss-match between server and client in Kilo

[Matt Riedemann]

On 3/9/2016 10:16 PM, Janki Chhatbar wrote:

Hi All

Greetings for the day!

I have noticed that while installing*OpenStack Kilo* using DevStack, the
server components cloned are stable/kilo whereas the client components
cloned are master. This leads to errors in installation or commands
miss-match. For eg.

_In tacker,_
tacker git repo is stable/kilo which points to incorrect git repo URL. I
have filled a  bug and proposed a patch for this
(https://bugs.launchpad.net/tacker/+bug/1555130)

_In Magnum_,
*magnum stable/kilo* clones *python-magnumclient master* which leads to
command mismatch (https://bugs.launchpad.net/magnum/+bug/1509273).

 1. Does this affect all other services?
 2. Does this mean that the branch needs to be changed for all the
service's clients? The change will be in /devstack/lib/{service}
file in "GITBRANCH" variable.

  If changes are required, I am willing to work on those.

Thanking you

Janki Chhatbar
OpenStack | SDN | Docker
(+91) 9409239106
simplyexplainedblog.wordpress.com 


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



Assuming the APIs in the server projects have not made backward 
incompatible changes since Kilo, the clients from master should continue 
to work. That's a big assumption with some projects, however.


If the clients on master implement CLIs for new features that landed 
after Kilo, then those won't work.


--

Thanks,

Matt Riedemann


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] Branch miss-match between server and client in Kilo

[Janki Chhatbar]

Hi All

Greetings for the day!

I have noticed that while installing* OpenStack Kilo* using DevStack, the
server components cloned are stable/kilo whereas the client components
cloned are master. This leads to errors in installation or commands
miss-match. For eg.

*In tacker,*
tacker git repo is stable/kilo which points to incorrect git repo URL. I
have filled a  bug and proposed a patch for this (
https://bugs.launchpad.net/tacker/+bug/1555130)

*In Magnum*,
*magnum stable/kilo* clones *python-magnumclient master* which leads to
command mismatch (https://bugs.launchpad.net/magnum/+bug/1509273).


   1. Does this affect all other services?
   2. Does this mean that the branch needs to be changed for all the
   service's clients? The change will be in /devstack/lib/{service} file in
   "GITBRANCH" variable.

 If changes are required, I am willing to work on those.

Thanking you

Janki Chhatbar
OpenStack | SDN | Docker
(+91) 9409239106
simplyexplainedblog.wordpress.com
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev