Open Stack

On Wed, May 27, 2015 at 4:26 AM, <ashish.jain14 at wipro.com> wrote:

> Dims,
>
> Thanks for this input. I hope this is done in nova-docker code?
>
> Regards
> Ashish
>
> ________________________________________
> From: Davanum Srinivas <davanum at gmail.com>
> Sent: Wednesday, May 27, 2015 3:44 PM
> To: Ashish Jain (WT01 - BAS)
> Cc: openstack at lists.openstack.org
> Subject: Re: [Openstack] [nova-docker][nova]Different meta data
> information in nova and docker view
>
> Ashish,
>
> when we create the docker container, we can pass it the name we want
> it to have, so yes, it's possible. you will have to try modifying the
> code to see the fallout.
>
> thanks,
> dims
>
> On Wed, May 27, 2015 at 5:12 AM,  <ashish.jain14 at wipro.com> wrote:
> >
> > Hello,
> >
> >
> > I am using nova-docker. I deploy a docker container and run the
> following 2 commands
> >
> > 1) nova list
> >
> +--------------------------------------+-------------------+--------+------------+-------------+-----------------------+
> > | ID                                   | Name              | Status |
> Task State | Power State | Networks              |
> >
> +--------------------------------------+-------------------+--------+------------+-------------+-----------------------+
> > | 35cdcbc6-516d-4e99-a8a1-28fedd5b088f | test123,and three | ACTIVE | -
>         | Running     | demo-net=192.168.1.71 |
> >
> +--------------------------------------+-------------------+--------+------------+-------------+-----------------------+
> >
> > 2) sudo docker ps
> > CONTAINER ID        IMAGE               COMMAND              CREATED
>          STATUS              PORTS               NAMES
> > ad381f97816d        httpd:2             "httpd-foreground"   34 minutes
> ago      Up 34 minutes
>  nova-35cdcbc6-516d-4e99-a8a1-28fedd5b088f
> >
> >
> > Why is their a difference in the name of the container? It is possible
> to somehow customize what is being seen in the docker view. for example map
> the Name field in Nova to NAMES field in docker?
> >
> > Regards
> > Ashish
> >
> >
> >
> >
> > The information contained in this electronic message and any attachments
> to this message are intended for the exclusive use of the addressee(s) and
> may contain proprietary, confidential or privileged information. If you are
> not the intended recipient, you should not disseminate, distribute or copy
> this e-mail. Please notify the sender immediately and destroy all copies of
> this message and any attachments. WARNING: Computer viruses can be
> transmitted via email. The recipient should check this email and any
> attachments for the presence of viruses. The company accepts no liability
> for any damage caused by any virus transmitted by this email.
> www.wipro.com
> >
> > _______________________________________________
> > Mailing list:
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
> > Post to     : openstack at lists.openstack.org
> > Unsubscribe :
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>
>
>
> --
> Davanum Srinivas :: https://twitter.com/dims
> The information contained in this electronic message and any attachments
> to this message are intended for the exclusive use of the addressee(s) and
> may contain proprietary, confidential or privileged information. If you are
> not the intended recipient, you should not disseminate, distribute or copy
> this e-mail. Please notify the sender immediately and destroy all copies of
> this message and any attachments. WARNING: Computer viruses can be
> transmitted via email. The recipient should check this email and any
> attachments for the presence of viruses. The company accepts no liability
> for any damage caused by any virus transmitted by this email.
> www.wipro.com
>
> _______________________________________________
> Mailing list:
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
> Post to     : openstack at lists.openstack.org
> Unsubscribe :
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>

Hi Ashish,

As Dims pointed out you could certainly change this and provide the same
display name that you provided to Nova to Docker.  The problem however is
that you probably don't want to do that.  Using Nova's UUID for the
container name in Docker is going to solve a number of head-aches and
potential problems for you.  Not the least of which is consistency.  The
"nova-<uuid>" has been useful for many to easily identify containers that
are managed/owned by Nova, it makes sense to do things this way in most
cases I think.

Is there an advantage that you see in using Nova's display name property
instead of the UUID here?

Thanks,
John
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack/attachments/20150527/c43503f2/attachment.html>