- summary: Duplication of build when provisioing enviroments --> Duplication of build when provisioning environments
When attempting to provision an entire environment I see nodes intended for one datacentre appearing in another. See example below:
command run:
ant -Denterprise=Genesis -Dservice=Provisioning -Denvironment=Production -Dapplication=FC9i386DB FC9i386DB:build
tree output:
build
`-- Genesis
`-- Provisioning
`-- Production
|-- London
| `-- rck01
| |-- lnrck01gen01
| | `-- FC9i386DB
| | `-- FC9i386DB.cfg
| |-- lnrck01gen02
| | `-- FC9i386DB
| | `-- FC9i386DB.cfg
| `-- nyrck01gen01
| `-- FC9i386DB
| `-- FC9i386DB.cfg
`-- NewYork
`-- rck01
|-- lnrck01gen01
| `-- FC9i386DB
| `-- FC9i386DB.cfg
|-- lnrck01gen02
| `-- FC9i386DB
| `-- FC9i386DB.cfg
`-- nyrck01gen01
`-- FC9i386DB
`-- FC9i386DB.cfg
As you can see there are nodes specified for London appearing in NewYork and vice versa. It seems that this only occurs at the environment level. This doesn't happen when provisioning datacentre or racks.