We have a development server for code changes.  Do we need to use dev  to 
test RE jobs (data changes?).  I could see if Development modeled  
production.  However our dev does not model prod because the foundation  
discovery 
pushes data to prod TOPO.  Can we use the sandbox to test RE  jobs?
 
For code changes, patches, etc we use DEV to Prod.
 
We are just not sure about the best approach for "data changes" made by the 
 RE jobs.  We want to be able to test the RE jobs.
 
I need to build a RE job that adds CI's to BMC.ASSET and /or the  sandbox.  
And I need to build a second RE job to update CI's where the host  name = 
host name, and the bios serial # = serial #.
 
We just do not want the data in production messed up as a result of the RE  
job.  Isn't this what the sandbox is for?
 
 
 
 
In a message dated 3/19/2010 9:53:52 P.M. Eastern Daylight Time,  
[email protected] writes:

**   
Afraid the bottom line  is that Topo should be sending data to Dev.
A Dev version of Topo.  Two instances of the Topo system.
 
How else do you test  new versions, patches etc. without lighting a fire 
under your Prod  system?
 
There should always be  a DEV, QA/Testing and Prod environment.
 
(there could be a 100  post long diatribe from various quarters about what 
constitutes appropriate  DEV, QA, Prod environments and how much the same 
they need to be to be  considered a replicated environment at this point).
 
Then there is the 4th,  a Sandbox for testing out products, theories, 
things that may or may not end  up on the path to production.
 
However, there should  always be those 3, same OS, Same DB, same ARsystem 
version patches  etc. etc. you get the picture,
 
QA/Testing should mimic  the real Production Environment.
 
In a big shop, QA/Testing should be the  same hardware as Production.
 
Haven't come up with a good argument why  the others can't be virtual,
and in theory there is good reason for  them to be virtual.
 
..... Dan


 
____________________________________
 From: Action Request System discussion list(ARSList)  
[mailto:[email protected]] On Behalf Of Kathy Morris
Sent:  March 19, 2010 6:39 PM
To: [email protected]
Subject:  Re: RE Jobs



**   
Discovery is pushing data into Topo on our production environment.   My 
concern is if we copy prod to dev, won't the data be different for the  
reconciliation jobs?  The data is continually being updated Discovery  pushing 
data 
into TOPO on Production.  Discovery does not push the  data into Topo on 
Dev.  It just seems that the RE are so  tempermental.  I am concerned that Dev 
will have different data (without  the updates from Discovery).  Right now 
I know we are not connecting  Discovery to Dev.
 
 
In a message dated 3/19/2010 6:27:47 P.M. Eastern Daylight Time,  
[email protected] writes:

**     
 
I  would highly recommend building a dev environment.  Setting up  
reconciliation jobs is not necessarily an easy task and is very error  prone. 
Also,  depending on how Discovery gets data into your production database, 
you may  be able to have it feed both environments.  If Remedy is pulling  
data (using AIE to transfer the data) into production, you can simply set up  
the same AIE jobs on your dev server for it to copy the same data into that 
 environment.  If, however, Discovery is pushing data into Remedy  (less 
likely) then you’d have to look for other options.  In fact, one  other option 
might be to configure AIE to actually pull CI data from  production… 
Lyle 
 
From: Action Request  System discussion list(ARSList) 
[mailto:[email protected]] On Behalf Of  Kathy Morris
Sent: Friday, March 19, 2010 3:56  PM
To: [email protected]
Subject: RE  Jobs
**  
 
Hi  All,
 

 
We  do not have a CMDB dev environment.  I need to create RE jobs.  Is  it 
better to copy BMC.ASSET into separate dataset, and run the RE job  against 
the dataset copy to testing purposes.  Or should we build a  separate DEV 
environment and create the RE job?  We also have only 1  Discovery Server that 
is connected to Production.  So the CMDB  development server would not 
receive any asset updates from the Discovery  tool.
 

 

 

 

_attend WWRUG10 www.wwrug.com ARSlist: "Where the Answers  Are"_ 
 


NOTICE: This email message is for the sole use of the  intended 
recipient(s) and may contain confidential and privileged  information. Any 
unauthorized 
review, use, disclosure or distribution is  prohibited. If you are not the 
intended recipient, please contact the sender  by reply email and destroy 
all copies of the original  message.





_attend WWRUG10 www.wwrug.com  ARSlist: "Where the Answers  Are"__attend 
WWRUG10 www.wwrug.com  ARSlist: "Where the Answers Are"_ _attend WWRUG10 
www.wwrug.com ARSlist:  "Where the Answers Are"_

_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
attend wwrug10 www.wwrug.com ARSlist: "Where the Answers Are"

Reply via email to