Ubuntu – How to specify ec2 instance types for different services

amazon ec2juju

After I have specified a default EC2 instance type for my Juju charm, how do I override that for one of the services?

For instance, the Juju tutorial deploys wordpress and mysql, and I can set the default-instance-type in my environments.yaml so both services are m1.small

But how do I configure it so that (only) the mysql service gets deployed on an instance type better suited to a database, like m2.xlarge ?

Best Answer

In summary, if you wanted to deploy with m2.xlarge:

 juju deploy mysql --constraints 'instance-type=m2.xlarge'

Or if you want your deployment script to be more portable between providers:

 juju deploy mysql --constraints 'mem=8G'

Here are the corresponding documents:

https://jujucharms.com/docs/2.0/reference-constraints

Related Solutions

Ubuntu – How to adjust the instance size that Juju uses

As per this section of the documentation you need to define the instance-type as part of a machine constraint:

Deploy MySQL on a machine with at least 32GiB of RAM, and at least 8 ECU of CPU power (architecture will be inherited from the environment, or default to amd64):
juju deploy --constraints "cpu-cores=8 mem=32G" mysql
Deploy to t1.micros on AWS:
juju bootstrap --constraints "cpu-power=0 mem=512M"
Launch all future "mysql" machines with at least 8GiB of RAM and 4 ECU:
juju set-constraints --service mysql mem=8G cpu-cores=4

Juju – How to Fix Juju Services Not Deploying Correctly

Tha it's work! I again install ubuntu server and this time everything goes well but one thing. Now when I juju status I see this:

2012-10-04 13:32:21,110 INFO Connected to environment.
machines:
  0:
    agent-state: running
    dns-name: node-00127968a7be.local
    instance-id: /MAAS/api/1.0/nodes/node-ab7c5eb6-0e08-11e2-bb37-001185e67955/
    instance-state: unknown
  1:
    agent-state: running
    dns-name: node-001185e677fe
    instance-id: /MAAS/api/1.0/nodes/node-82beae92-0e09-11e2-a134-001185e67955/
    instance-state: unknown
  2:
    agent-state: running
    dns-name: node-001185e6772b.local
    instance-id: /MAAS/api/1.0/nodes/node-5c21dc18-0e0a-11e2-a134-001185e67955/
    instance-state: unknown
services:
  mysql:
    charm: cs:precise/mysql-8
    relations:
      db:
      - wordpress
    units:
      mysql/0:
        agent-state: started
        machine: 1
        public-address: node-001185e677fe.localdomain
  wordpress:
    charm: cs:precise/wordpress-9
    exposed: true
    relations:
      db:
      - mysql
      loadbalancer:
      - wordpress
    units:
      wordpress/0:
        agent-state: started
        machine: 2
        open-ports:
        - 80/tcp
        public-address: node-001185e6772b.local

public adress seems be strange because it's name of my nodes. I check on my router adress of node where is wordpress and type on webbrowser but I get

502 Bad Gateway nginx/1.1.19

I don't know what to do. Please help me.

Best Answer

Related Solutions

Ubuntu – How to adjust the instance size that Juju uses

Juju – How to Fix Juju Services Not Deploying Correctly

Related Question