JUJU Charm Certification

[SivaRamaPrasad Ravipati]

Hi,

I have installed the openstack cloud using openstack Autopilot. I am
trying to deploy juju-gui in the internal juju environment.




I did the following.
====================

->From MAAS node

$export JUJU_HOME=~/.cloud-install/juju

-> Connecting Landscape server to deploy our charm  and add relation
to cinder charm.

$juju ssh landscape-server/0 sudo
'JUJU_HOME=/var/lib/landscape/juju-homes/`sudo ls -rt
/var/lib/landscape/juju-homes/ | tail -1` sudo -u landscape -E bash'

-> From Landscape Server

landscape at juju-machine-0-lxc-1:~$ juju deploy cs:juju-gui-134

Added charm "cs:trusty/juju-gui-134" to the environment.


ubuntu at juju-machine-0-lxc-1:~$ juju status
	
"4":
    agent-state: error
    agent-state-info: 'cannot run instances: cannot run instances:
gomaasapi: got
      error back from server: 409 CONFLICT (No available node matches
constraints:
      zone=region1)'
    instance-id: pending
    series: trusty





 juju-gui:
    charm: cs:trusty/juju-gui-134
    exposed: false
    service-status:
      current: unknown
      message: Waiting for agent initialization to finish
      since: 07 Sep 2016 06:46:22Z
    units:
      juju-gui/1:
        workload-status:
          current: unknown
          message: Waiting for agent initialization to finish
          since: 07 Sep 2016 06:46:22Z
        agent-status:
          current: allocating
          since: 07 Sep 2016 06:46:22Z
        agent-state: pending
        machine: "4"


JUJU Version
=============		

ubuntu at juju-machine-0-lxc-1:~$ juju --version
1.25.6-trusty-amd64
	

My assumption

=============

It looks like we need to define a pool of servers in a region called region1.


I have a question. Once we have Ubuntu OpenStack Autopilot deployment,
If we need to deploy any Charm externally we need to add a sever to
MAAS?

How can I solve this Issue. Please provide me some solution.


Thanks,

Siva.


On Mon, Aug 29, 2016 at 9:36 PM, Mark Shuttleworth <mark at ubuntu.com> wrote:

> On 29/08/16 11:23, SivaRamaPrasad Ravipati wrote:
> > How to get my newly created juju charm into the Charm store as a
> > Ubuntu certified (or) recommended (Official) Charm?
> >
> > Is Charm Certification  paid One?
> >
>
> The "curated" charms are the ones that anybody can deploy directly, as
> in "juju deploy charmname". Those are charms that have been reviewed and
> meet policy requirements, and we are confident that the maintainers of
> the charms will keep them up to date as everything around them continues
> to evolve. There is no charge for that, it's like maintaining packages
> in Ubuntu, as long as you show that you care and can do it well then
> welcome to the community!
>
> Key questions these folks will ask:
>
>  * do your charms support the full lifecycle - install, scale up, scale
> back, upgrade
>  * do your charms integrate with the likely monitoring and management
> things people care about
>  * do your charms work with the likely other components (i.e. neutron or
> cinder in openstack)
>  * are they built with tests and other indicators of quality and
> maintenance
>  * is there a commitment to keeping them in good condition over time
>
> > How can I integrate myCharm into ubuntu-Autopilot?
>
> That's a separate conversation, I would suggest you start with Mark
> Baker cc'd. The main things we care about for Autopilot, in terms of the
> charms, are:
>
>  * are the charms being tested daily in OIL (OpenStack Interop Lab)
>  * do they have a high success rate in OIL?
>  * are there versions of the charms that work with OpenStack trunk and
> stable (i.e. Mitaka and Newton)
>  * are we confident there will be a Newton-safe version of the charm
> when Newton releases?
>    - mainly we look for upstream CI/CD with these charms againts stable
> and trunk OpenStack
>  * is there CI of the next version of the charmed software (i.e. will
> there be charms of your next release)
>
> Mark
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/juju/attachments/20160907/5f6c9001/attachment.html>