brooklyn-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Aled Sage <aled.s...@cloudsoftcorp.com>
Subject Re: Fwd: Siemens SoW
Date Wed, 18 Feb 2015 17:33:16 GMT
Please ignore; sent to wrong list!


On 18/02/2015 17:14, Aled Sage wrote:
> Devs,
>
> Before we allocate someone to this, does anyone have existing 
> experience with ServiceNow: for deployments via the SNOW cloud 
> orchestration / service catalog; and for reporting service metrics 
> back in to SNOW service management service?
>
> This is just for an initial look: to "grab a test / pilot account from 
> SNOW and begin to look at the API integration aspects, art of the 
> possible etc".
>
> If not, we'll just have to allocate someone (even though everyone is 
> already really busy!)
>
> Aled
>
>
> On 18/02/2015 16:50, Duncan Johnston Watt wrote:
>> Aled
>>
>> Can someone look into SNOW - see below.
>>
>> Best
>>
>> Duncan
>>
>> ---------- Forwarded message ----------
>> From: *Ratcliffe, Darren* <darren.ratcliffe@canopy-cloud.com 
>> <mailto:darren.ratcliffe@canopy-cloud.com>>
>> Date: 18 February 2015 at 07:53
>> Subject: Siemens SoW
>> To: Duncan Johnston-Watt <duncan.johnstonwatt@cloudsoftcorp.com 
>> <mailto:duncan.johnstonwatt@cloudsoftcorp.com>>
>> Cc: "Jackson, Adam" <adam.jackson@canopy-cloud.com 
>> <mailto:adam.jackson@canopy-cloud.com>>
>>
>>
>> Hi Duncan,
>>
>> Yesterday I approved the Siemens SoW PO so you should have it soon, I 
>> also sat down with our CEVP who runs our MS business and his Siemens 
>> leadership team yesterday to walk through how we need to support near 
>> term cloud activities there.
>>
>> In essence it is nothing more than what we understand today:
>>
>> ·Integrate Brooklyn with SNOW (ServiceNow) < new SoW
>>
>> oFor deployments via the SNOW cloud orchestration \ service catalog
>>
>> oReport service metrics back in to SNOW service management service
>>
>> ·Integrate Brooklyn with: < vCAC SoW
>>
>> oCanopy EPC’s (Enterprise Private Cloud) - vCAC
>>
>> oAtos DDC (Digital Data Centre) - vCAC
>>
>> oEMC EHC (Enterprise Hybrid Cloud) – vCAC
>>
>> oAWS
>>
>> To be clear 20 days is just to get us started and isn’t my view of 
>> how long it will take to complete, the carrot to both of us for this 
>> specific activity is that the CEVP informed me today we manage 20k of 
>> the 85k servers in the Siemens estate and we have been asked to 
>> implement a service to capture this capacity and move to cloud as 
>> part of the refresh.
>>
>> *I am putting a permanent 2 man team in to the Siemens account team 
>> and this will take a few days to put in place, in the meantime can 
>> you get one of your guys to grab a test / pilot account from SNOW and 
>> begin to look at the API integration aspects, art of the possible etc*
>>
>> Thanks
>>
>> Darren
>>
>>
>>
>>
>> -- 
>> Duncan Johnston-Watt
>> CEO | Cloudsoft Corporation
>>
>> Twitter| @duncanjw
>> Mobile| +44 777 190 2653
>> Skype| duncan_johnstonwatt
>> Linkedin| www.linkedin.com/in/duncanjohnstonwatt 
>> <http://www.linkedin.com/in/duncanjohnstonwatt>
>>
>> Cloudsoft Corporation Limited, Registered in Scotland No: SC349230.  
>> Registered Office: 13 Dryden Place, Edinburgh, EH9 1RP
>>
>> This e-mail message is confidential and for use by the addressee 
>> only. If the message is received by anyone other than the addressee, 
>> please return the message to the sender by replying to it and then 
>> delete the message from your computer. Internet e-mails are not 
>> necessarily secure. Cloudsoft Corporation Limited does not accept 
>> responsibility for changes made to this message after it was sent.
>>
>> Whilst all reasonable care has been taken to avoid the transmission 
>> of viruses, it is the responsibility of the recipient to ensure that 
>> the onward transmission, opening or use of this message and any 
>> attachments will not adversely affect its systems or data. No 
>> responsibility is accepted by Cloudsoft Corporation Limited in this 
>> regard and the recipient should carry out such virus and other checks 
>> as it considers appropriate.
>


Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message