kiranchavala commented on issue #31:
URL:
https://github.com/apache/cloudstack-terraform-provider/issues/31#issuecomment-1983179868
Closing the issue as the issue is not reproducible on the latest build
--
This is an automated message from the Apache Git Service.
To respond to the
kiranchavala closed issue #31: Failure to add secondary IP to a NIC for a VM in
a project
URL: https://github.com/apache/cloudstack-terraform-provider/issues/31
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL
kiranchavala commented on issue #31:
URL:
https://github.com/apache/cloudstack-terraform-provider/issues/31#issuecomment-1978939126
@Pearl1594
Not able to reproduce the issue, I was able to deploy a vm and add secondary
IP to a NIC for a VM in a project.
Let me know if can
DaanHoogland commented on issue #31:
URL:
https://github.com/apache/cloudstack-terraform-provider/issues/31#issuecomment-1028160773
> @DaanHoogland I wonder why it worked for you. Perhaps you're using a
global admin that can see all VMs in all projects?
Yes, i did.
--
This is an
onitake commented on issue #31:
URL:
https://github.com/apache/cloudstack-terraform-provider/issues/31#issuecomment-1028143924
@Pearl1594 It sounds to me like this is a problem with your
cloudstack_secondary_ipaddress.default resource. It lacks all the parameters
the other resources have
DaanHoogland commented on issue #31:
URL:
https://github.com/apache/cloudstack-terraform-provider/issues/31#issuecomment-1026878010
not sure what your issue was but something else must have been in play,
@Pearl1594 . Note however that I executed it in a simulated environment.
--
This
deployed without errors. I checked if the network existed in the project and if
the VM had a secondary ip. all good. also destroying went without error
messages.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above
Pearl1594 edited a comment on issue #31:
URL:
https://github.com/apache/cloudstack-terraform-provider/issues/31#issuecomment-1025625833
@DaanHoogland I was able to do it directly on ACS, so I believe it's a
limitation on the provider end - only when the scope is within a project. The
Pearl1594 commented on issue #31:
URL:
https://github.com/apache/cloudstack-terraform-provider/issues/31#issuecomment-1025625833
I was able to do it directly on ACS, so I believe it's a limitation on the
provider end - only when the scope is within a project. The issue I believe is
that
DaanHoogland commented on issue #31:
URL:
https://github.com/apache/cloudstack-terraform-provider/issues/31#issuecomment-1025620436
@Pearl1594 is this a cloudstack issue? I.E. does the API allow the action
that the tf provider can't?
--
This is an automated message from the Apache Git
ember 2017 00:14
An: dev@cloudstack.apache.org
Betreff: Re: 4.9 / 4.10 KVM + openvswitch + vpc + static nat /
secondary ip on eth2?
Hi Frank,
Great analysis, but what can we do now? Is there a workaround or who
can fix this?
CLOUDSTACK-10127
Greetings
Sven
-Ursprüngliche Nachricht-
Von: Vogel, Sven [mailto:sven.vo...@kupper-computer.com]
Gesendet: Mittwoch, 1. November 2017 00:14
An: dev@cloudstack.apache.org
Betreff: Re: 4.9 / 4.10 KVM + openvswitch + vpc + static na
@cloudstack.apache.org
Betreff: Re: 4.9 / 4.10 KVM + openvswitch + vpc + static nat / secondary ip on
eth2?
Hi Frank,
Great analysis, but what can we do now? Is there a workaround or who can fix
this?
Greetings
Sven
Am 31.10.2017 um 22:41 schrieb Frank Maximus
<frank.maxi...@nuagenetworks.
rfaces and trunk (0,129,180,100-1500) to cloudbr0
Cloudbr0 (0 - guest network)
Fakebridge pub129 (public network)
Fakebridge sto180 (secondary storage network)
Fakebridge mgmt0 (management)
If I have a vpc all things work until I add a secondary ip and add a
static nat.
The
s not solved correctly.
>>
>> 1. KVM
>> 2. Bridges
>> bond with two interfaces and trunk (0,129,180,100-1500) to cloudbr0
>> Cloudbr0 (0 - guest network)
>> Fakebridge pub129 (public network)
>> Fakebridge sto180 (secondary storage network
"network": "192.168.1.0/24",
"nic_dev_id": "2",
"nw_type": "guest",
"one_to_one_nat": false,
"public_ip": "192.168.1.254",
"size": "24",
&qu
trunk (0,129,180,100-1500) to cloudbr0
> Cloudbr0 (0 - guest network)
> Fakebridge pub129 (public network)
> Fakebridge sto180 (secondary storage network)
> Fakebridge mgmt0 (management)
>
> If I have a vpc all things work until I add a secondary ip and add a
>
Cloudbr0 (0 - guest network)
Fakebridge pub129 (public network)
Fakebridge sto180 (secondary storage network)
Fakebridge mgmt0 (management)
If I have a vpc all things work until I add a secondary ip and add a static
nat.
The following will happen, first address
GitHub user wido opened a pull request:
https://github.com/apache/cloudstack/pull/2028
CLOUDSTACK-9853: Add support for Secondary IPv6 Addresses and Subnets
This commit adds support for passing IPv6 Addresses and/or Subnets as
Secondary IPs.
This is groundwork for
Github user SudharmaJain commented on the issue:
https://github.com/apache/cloudstack/pull/1909
@niteshsarda I see a problem here. The listNics command can be used to list
both primary and secondary ips. In case if we pass nicid parameter with it, i
feel we should use keywork to
Github user ustcweizhou commented on the issue:
https://github.com/apache/cloudstack/pull/1909
@niteshsarda in my opinion, what we should change is the search processing,
not the process on creating nic response.
to be clear, in server/src/com/cloud/network/NetworkServiceImpl.java
Github user niteshsarda commented on the issue:
https://github.com/apache/cloudstack/pull/1909
