You wont have to share your MSDN credentials.  You can add me as a user in
your Azure account.  I should be able to access it.

I can't do it via RDP because cloning an image is done at the Azure level,
not at the VM level.  Something along these lines:
https://devblogs.microsoft.com/cse/2018/02/15/copy-custom-vm-images-on-azure/

Thanks
Om

On Mon, Apr 13, 2020 at 12:24 AM Alex Harui <[email protected]>
wrote:

> I don't think I should be giving out my MSDN credentials.  If you can
> install other shell capabilities or access the image via RDP, go for it.
> If there is some secure way to share the image let me know what it is.  I
> don't know much about Azure.
>
> -Alex
>
> On 4/13/20, 12:02 AM, "Yishay Weiss" <[email protected]> wrote:
>
>     Related, as most (all?) of the instructions don’t require anything but
> a shell wouldn’t it be easier and faster to access the machine with ssh
> [1], rather than using remote desktop?
>
>     [1]
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fwindows-server%2Fadministration%2Fopenssh%2Fopenssh_install_firstuse&amp;data=02%7C01%7Caharui%40adobe.com%7Cd6686c50bc5a47593a2c08d7df78952a%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637223581303726403&amp;sdata=sC9JtN12VWCQ7PgzeyWNpn8NlwO1jdDaHbdfuwVjwo0%3D&amp;reserved=0
>
>     From: Yishay Weiss<mailto:[email protected]>
>     Sent: Monday, April 13, 2020 9:55 AM
>     To: [email protected]<mailto:[email protected]>
>     Subject: RE: Prioritize Release Jobs on CI
>
>     Can’t you do that with remote desktop?
>
>     ________________________________
>     From: OmPrakash Muppirala <[email protected]>
>     Sent: Monday, April 13, 2020 9:51:25 AM
>     To: Apache Royale Development <[email protected]>
>     Subject: Re: Prioritize Release Jobs on CI
>
>     Alex,
>
>     I believe this is your personal Azure subscription right?  Any chance
> I can
>     get access to it so I can try to copy the image out the machine and
>     redeploy it somewhere else?
>
>     Thanks,
>     Om
>
>     On Sun, Apr 12, 2020 at 6:18 PM OmPrakash Muppirala <
> [email protected]>
>     wrote:
>
>     > I can help set this up on Azure.  Give me some time to work out the
>     > details?
>     >
>     > Thanks,
>     > Om
>     >
>     > On Sun, Apr 12, 2020, 11:49 AM Harbs <[email protected]> wrote:
>     >
>     >> OK. Good to know.
>     >>
>     >> > On Apr 12, 2020, at 9:45 PM, Alex Harui <[email protected]
> >
>     >> wrote:
>     >> >
>     >> > FWIW, I just looked and the longest job in the release steps so
> far is
>     >> 8 minutes.  Most are under 2 minutes.  There might be jobs later
> that take
>     >> longer that we haven't run yet.  IMO, the issue isn't speed of the
> machine,
>     >> it is just that we are sharing the machine with longer jobs (1 hour
> for
>     >> TourDeFlexMigration).  And again, the machine will be idle for
> stretches of
>     >> time while the RM verifies artifacts after each step.
>     >> >
>     >> > -Alex
>     >> >
>     >> > On 4/12/20, 11:32 AM, "Harbs" <[email protected] <mailto:
>     >> [email protected]>> wrote:
>     >> >
>     >> >    Fair enough.
>     >> >
>     >> >    I expect builds to be somewhere between 10 and 20 times faster
> on a
>     >> powerful machine.
>     >> >
>     >> >    Yeah. It’s probably going to be a bit of work changing the
> server,
>     >> but probably worth it in the long run.
>     >> >
>     >> >    I think I’ll try this when I do the next release unless Yishay
> wants
>     >> to work with me on this for this release — but I’m not going to be
> able to
>     >> help until after Passover (i.e. next week).
>     >> >
>     >> >    Thanks,
>     >> >    Harbs
>     >> >
>     >> >> On Apr 12, 2020, at 9:22 PM, Alex Harui <[email protected]
> >
>     >> wrote:
>     >> >>
>     >> >> The Azure portal says: Standard F2s_v2 (2 vcpus, 4 GiB memory)
>     >> >>
>     >> >> I think I am reading changes to the build process in your
>     >> suggestions.  I do not really want to spend more of my time on this
>     >> process.  But if you want to do the work, that's fine with me.
>     >> >>
>     >> >> -Alex
>     >> >>
>     >> >> On 4/12/20, 10:57 AM, "Harbs" <[email protected] <mailto:
>     >> [email protected]> <mailto:[email protected] <mailto:
>     >> [email protected]>>> wrote:
>     >> >>
>     >> >>   What kind of horsepower is included in the free Azure account?
>     >> >>
>     >> >>   The server I mentioned builds (considerably) faster than my own
>     >> local machine. The ci server seems to build many times slower.
>     >> >>
>     >> >>   One thing we can do to minimize running server time would be to
>     >> transfer the artifacts to storage instead of keeping them on the
> server. On
>     >> AWS, I’d probably use S3. Not sure what the similar service on
> Azure is
>     >> called.
>     >> >>
>     >> >>> On Apr 12, 2020, at 8:26 PM, Alex Harui
> <[email protected]
>     >> <mailto:[email protected]>> wrote:
>     >> >>>
>     >> >>> OK, that's pretty much how I understand Azure as well.  The key
> thing
>     >> is that "running" includes time where the CI server is not running
> any
>     >> Jenkins jobs.  The CI Server steps might take only a few hours of
> actual
>     >> server time, but there is time where the RM is verifying artifacts
> locally
>     >> so you'd be paying for that or the RM would have to keep shutting
> down and
>     >> restarting.
>     >> >>>
>     >> >>> Seems like it would be cheaper/simpler to get the free MSDN
> account
>     >> and leave it running.
>     >> >>>
>     >> >>> -Alex
>     >> >>>
>     >> >>> On 4/12/20, 10:15 AM, "Harbs" <[email protected] <mailto:
>     >> [email protected]>> wrote:
>     >> >>>
>     >> >>>  My experience is with AWS.
>     >> >>>
>     >> >>>  I assume Microsoft has similar offerings, but I don’t have
>     >> experience with Azure.
>     >> >>>
>     >> >>>  AWS has on-demand EC2 instances which you pay for only the
> actual
>     >> time that they are running.[1]
>     >> >>>
>     >> >>>  Instances can be started and stopped via command line (or via
> the
>     >> web interface) as long as you have valid credentials to do so.
>     >> >>>
>     >> >>>  For example: an m5.4xlarge instance has 16 cores and costs
> about
>     >> $1.5 per hour. On a machine like that, a full build would probably
> take
>     >> less than 10 minutes. It’s probably possible to do a full release
> with only
>     >> a few hours of server time.
>     >> >>>
>     >> >>>  Leaving a server like that running all the time would get
> expensive,
>     >> but if it’s just spun up for releases, you’d get very fast builds
> at a
>     >> reasonable price.
>     >> >>>
>     >> >>>  I’d be happy to pay $10-$50 (and possibly more) per release to
> make
>     >> the release process painless for the RM.
>     >> >>>
>     >> >>>  [1]
>     >>
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Faws.amazon.com%2Fec2%2Fpricing%2Fon-demand%2F&amp;data=02%7C01%7Caharui%40adobe.com%7Cd6686c50bc5a47593a2c08d7df78952a%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637223581303726403&amp;sdata=EyaZ2qgR4pX3JWE5YFr6Ze38L53aPT5VRNMW5pPpLxw%3D&amp;reserved=0
>     >> <
>     >>
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Faws.amazon.com%2Fec2%2Fpricing%2Fon-demand%2F&amp;data=02%7C01%7Caharui%40adobe.com%7Cd6686c50bc5a47593a2c08d7df78952a%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637223581303726403&amp;sdata=EyaZ2qgR4pX3JWE5YFr6Ze38L53aPT5VRNMW5pPpLxw%3D&amp;reserved=0
>     >> ><
>     >>
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Faws.amazon.com%2Fec2%2Fpricing%2Fon-demand%2F&amp;data=02%7C01%7Caharui%40adobe.com%7Cd6686c50bc5a47593a2c08d7df78952a%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637223581303726403&amp;sdata=EyaZ2qgR4pX3JWE5YFr6Ze38L53aPT5VRNMW5pPpLxw%3D&amp;reserved=0
>     >> <
>     >>
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Faws.amazon.com%2Fec2%2Fpricing%2Fon-demand%2F&amp;data=02%7C01%7Caharui%40adobe.com%7Cd6686c50bc5a47593a2c08d7df78952a%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637223581303726403&amp;sdata=EyaZ2qgR4pX3JWE5YFr6Ze38L53aPT5VRNMW5pPpLxw%3D&amp;reserved=0
>     >> >><
>     >>
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Faws.amazon.com%2Fec2%2Fpricing%2Fon-demand%2F&amp;data=02%7C01%7Caharui%40adobe.com%7Cd6686c50bc5a47593a2c08d7df78952a%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637223581303736397&amp;sdata=DqPTaehUf%2BOiwMfu9jJ%2B6ftsInmiyYYccO6bRT%2BzYTs%3D&amp;reserved=0
>     >> <
>     >>
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Faws.amazon.com%2Fec2%2Fpricing%2Fon-demand%2F&amp;data=02%7C01%7Caharui%40adobe.com%7Cd6686c50bc5a47593a2c08d7df78952a%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637223581303736397&amp;sdata=DqPTaehUf%2BOiwMfu9jJ%2B6ftsInmiyYYccO6bRT%2BzYTs%3D&amp;reserved=0
>     >> ><
>     >>
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Faws.amazon.com%2Fec2%2Fpricing%2Fon-demand%2F&amp;data=02%7C01%7Caharui%40adobe.com%7Cd6686c50bc5a47593a2c08d7df78952a%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637223581303736397&amp;sdata=DqPTaehUf%2BOiwMfu9jJ%2B6ftsInmiyYYccO6bRT%2BzYTs%3D&amp;reserved=0
>     >> <
>     >>
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Faws.amazon.com%2Fec2%2Fpricing%2Fon-demand%2F&amp;data=02%7C01%7Caharui%40adobe.com%7Cd6686c50bc5a47593a2c08d7df78952a%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637223581303736397&amp;sdata=DqPTaehUf%2BOiwMfu9jJ%2B6ftsInmiyYYccO6bRT%2BzYTs%3D&amp;reserved=0
>     >> >>>
>     >> >>>
>     >> >>>> On Apr 12, 2020, at 7:45 PM, Alex Harui
> <[email protected]>
>     >> wrote:
>     >> >>>>
>     >> >>>> I'm not very experienced with spinning up servers.  The CI
> server we
>     >> are using is effectively free, based on a generous donation from
> Microsoft
>     >> of MSDN accounts to ASF committers.  So I leave it up 24/7, and
> share the
>     >> RDP access on private@.  I think any other ASF committer could do
> the
>     >> same.  IIRC, if that server actually is stopped, I have to use my
> personal
>     >> (unshared) MSDN credentials to start it again.   AIUI, if I
> actually paid
>     >> for the server, it would cost me to leave it running even if it
> didn't run
>     >> jobs between releases.
>     >> >>>>
>     >> >>>> Is that what you are basically saying?  I think it might be
> best if
>     >> another committer got a CI server going via the MS donation and
> could leave
>     >> it up 24/7.
>     >> >>>>
>     >> >>>> -Alex
>     >> >>>>
>     >> >>>> On 4/12/20, 9:28 AM, "Harbs" <[email protected]> wrote:
>     >> >>>>
>     >> >>>> I’m willing to do this.
>     >> >>>>
>     >> >>>> Considering that the release will be run infrequently, it
> should be
>     >> doable to have a relatively powerful server that could be spun up on
>     >> demand. This is something I have setup for my own releases.
>     >> >>>>
>     >> >>>> The only complication would be that each RM would need valid
>     >> credentials to spin up the server.
>     >> >>>>
>     >> >>>> Harbs
>     >> >>>>
>     >> >>>>> On Apr 12, 2020, at 7:10 PM, Alex Harui
> <[email protected]>
>     >> wrote:
>     >> >>>>>
>     >> >>>>> A better solution, IMO, is for someone else to offer up a CI
> server
>     >> only for release jobs.
>     >>
>     >>
>
>
>
>

Reply via email to