This is some more information:

juju clouds
Cloud        Regions  Default          Type        Description
aws               14  us-east-1        ec2         Amazon Web Services
aws-china          1  cn-north-1       ec2         Amazon China
aws-gov            1  us-gov-west-1    ec2         Amazon (USA Government)
azure             24  centralus        azure       Microsoft Azure
azure-china        2  chinaeast        azure       Microsoft Azure China
cloudsigma         5  hnl              cloudsigma  CloudSigma Cloud
google             8  us-east1         gce         Google Cloud Platform
joyent             6  eu-ams-1         joyent      Joyent Cloud
oracle 5 uscom-central-1 oracle Oracle Compute Cloud Service
rackspace          6  dfw              rackspace   Rackspace Cloud
localhost          1  localhost        lxd         LXD Container Hypervisor
*prodmaas           0                   maas        Metal As A Service*

the yaml file:

clouds:
   prodmaas:
      type: maas
      auth-types: [oauth1]
      endpoint: http://IP/MAAS


On 08/03/2017 04:39 PM, wahi wrote:
One additional infomration the JUJU version is 2.2


On 08/03/2017 04:08 PM, wahi wrote:
Hi Witod,

Thanks a lot for your response.

Nop the same error.


On 08/03/2017 04:04 PM, Witold Krecicki wrote:
Could you check if juju bootstrap maas-cloud maas-cloud-controller
--bootstrap-constraints mem=0 works?

On Thu, Aug 3, 2017 at 1:41 PM, wahi <[email protected]> wrote:
Hi Christian,

Thanks for your reply.

Yes I am seeing the VM with 4GB from MAAS web UI.


On 08/03/2017 02:32 PM, Christian Muirhead wrote:

Hi Wahi -
Can you look in the MAAS web UI and confirm that MAAS can see the 4GB of memory in the machine you expect? I've had a situation where I added ram to
a KVM but forgot to re-enlist the machine or update the ram in MAAS.
Cheers,
Christian


On Thu., 3 Aug. 2017, 19:13 wahi, <[email protected]> wrote:
Dear all,


Recently I am investingating the installation of Openstack using MAAS and
JUJU.

I installaed MAAS on bare metals server Ubuntu 16.04, I have another
server also which has Ubuntu 16.04.

I managed to deploy several KVM virtual machines on two servers using
MAAS, so every VM got private IP address form MAAS.


I installed JUJU package on a VM which is located on the second server
(not MAAS server), from there I did the following steps:

juju add-cloud /here I chose MAAS/

Here: Enter the API endpoint url: http://public_IP_OF_MAAS:5240/MAAS

juju bootstrap maas-cloud

juju clouds /maas-cloud is there/

juju add-credential maas-cloud /Entered the API key/

juju bootstrap maas-cloud maas-cloud-controller

after this command getting

Creating Juju controller "prodmaas-controller" on prodmaas

Looking for packaged Juju agent version 2.0.2 for amd64

Launching controller instance(s) on prodmaas...

ERROR failed to bootstrap model: cannot start bootstrap instance: cannot
run instances: cannot run instance: No available machine matches
constraints: [('zone', ['default']), ('agent_name',
['f7a273ac-6190-4798-8ee6-f7d2df722b27']), ('mem', ['3584'])] (resolved to
"mem=3584.0 zone=default")


I need to mention that I have a VM on MAAS server with 4GB memory!!! (I
don’t know if the error related to that)


Could you please help me to identify the problem.


Thank you very much in advance.



Regards,

Wahi

--
Juju mailing list
[email protected]
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/juju


--
Juju mailing list
[email protected]
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/juju





-- 
Juju mailing list
[email protected]
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

Reply via email to