|
Hi Chiradeep,
Thank you very much.
My problem has been solved. The reason is the space of my temp
primary storage had not enough.
After I added a new primary storage, the new ips was able to be
assigned.
Thank you for your teaching me using Cloudmonkey.
Regards,
Steven
On 12/17/2013 04:45 PM, Chiradeep Vittal wrote:
Cloudmonkey is very user friendly. Just <tab> if you
don't know the parameters
> list pods
count = 1
pod:
name = POD0
id = 83f13f18-7fa6-422b-be35-ecb8f4d75a9f
allocationstate = Enabled
endip = 172.16.15.200
gateway = 172.16.15.1
netmask = 255.255.255.0
startip = 172.16.15.2
zoneid = 640b7dff-c1a8-45d3-83b3-749614ae7225
zonename = Sandbox-simulator
> update pod
allocationstate= endip= gateway= id=
name= netmask= startip=
> update pod startip=172.16.15.2 endip=172.16.15.202
netmask=255.255.255.0 gateway=172.16.15.1
id=83f13f18-7fa6-422b-be35-ecb8f4d75a9f
pod:
name = POD0
id = 83f13f18-7fa6-422b-be35-ecb8f4d75a9f
allocationstate = Enabled
endip = 172.16.15.202
gateway = 172.16.15.1
netmask = 255.255.255.0
startip = 172.16.15.2
zoneid = 640b7dff-c1a8-45d3-83b3-749614ae7225
zonename = Sandbox-simulator
Thank you, Chiradeep.
I am not very familiar with cloudmonkey. Most time I just
uses it for "list".
Could you give me a example 'update pod'?
Thank you.
The following is the list of my two pods.
+--------------+------+--------------+-----------------+--------------------------------------+---------------+--------------------------------------+------------+----------+
| endip | name | startip | allocationstate
| zoneid | netmask
| id | gateway |
zonename |
+--------------+------+--------------+-----------------+--------------------------------------+---------------+--------------------------------------+------------+----------+
| 172.16.1.250 | pod1 | 172.16.1.230 | Enabled |
eaf557a8-2710-42a0-8ae1-ccd262c3f29c | 255.255.255.0 |
14de769a-16d6-4b4b-b4cd-6f088c5e1654 | 172.16.1.1 | zone1
|
| 172.16.2.250 | pod2 | 172.16.2.230 | Enabled |
eaf557a8-2710-42a0-8ae1-ccd262c3f29c | 255.255.255.0 |
cd558724-6a77-40fa-8df8-acd82f12911f | 172.16.2.1 | zone1
|
+--------------+------+--------------+-----------------+--------------------------------------+---------------+--------------------------------------+------------+----------+
On 12/16/2013 07:19 PM, Chiradeep Vittal wrote:
Steven, I assume you want to add ip addresses that are available to VMs.
I am also assuming that the IP for VMs is drawn from the pod ip range. In
that case, you can use the 'update pod' api with cloudmonkey.
On 12/16/13 1:44 PM, "Steven Liang" <[email protected]> wrote:
Hi James,
Thank you anyway.
But I don't understand what Mr. Chiradeep said.
I listed my pods using cloudmonkey, the two pods have the same netmask
and gateway(management ips).
What should I update? Please help me.
Thank you.
Steven
On 12/16/2013 04:35 PM, ogiljae wrote:
Hi,
Sorry about confusing.
The way I wrote is for advanced network not basic zone.
I believe that you should stick to Mr. Chiradeep's guide.
James.
On 12/17/13, 6:29 AM, Steven Liang wrote:
Hi Giljae,
I can not read your picture, can you send me again?
BTW, I didn't set any vlans, you mean I must set vlan?
Thank you.
Steven
On 12/16/2013 04:24 PM, giljae o wrote:
Hi,
You can add additional public ip addresses with the new vlan or
existing vlan on UI below.
Inline image 1
On Tue, Dec 17, 2013 at 5:27 AM, Steven Liang<[email protected]<mailto:[email protected]>> wrote:
Hi Chiradeep,
Thank you for updating.
I haven't tried. Can I use cloudmonkey? I've installed
cloudmonkey, just
used for "list".
Steven
On 12/16/2013 03:11 PM, Chiradeep Vittal wrote:
> Have you tried expanding your pod with
>
http://cloudstack.apache.org/docs/api/apidocs-4.2/root_admin/updatePod.
html
>
> On 12/16/13 7:22 AM, "Steven Liang"<[email protected]
<mailto:[email protected]>> wrote:
>
>> Hi All,
>>
>> I have a question. If I would use up my existing public
IPs(for
example:
>> xxx.xxx.1.0/24), how to add new subnet(xxx.xxx.2.0/24) to my
new pod?
>> Thank you.
>>
>> Steven
|
