Skip to content

Instantly share code, notes, and snippets.

@timfoster

timfoster/lullaby3-phase2-flag-day.md Secret

Last active February 26, 2019 16:20
Show Gist options
  • Save timfoster/1dc9fb5d8e2fd80e1c94e7987851b42d to your computer and use it in GitHub Desktop.
Save timfoster/1dc9fb5d8e2fd80e1c94e7987851b42d to your computer and use it in GitHub Desktop.
Download ZIP
Raw
lullaby3-phase2-flag-day.md

Flag day: Lullaby 3 - phase 2

Hi everyone,

We've finished integrating the second phase of the TOOLS-2043 changes, which converts most Triton components to using the build framework described as part of RFD 145.

You should update any local copies of repositories mentioned at the end of this message.

Rather than repeat all of the text in phase 1 flag day, you can read a copy of that here:

https://gist.github.com/timfoster/ebd30a91087ca2c09b2d68a03ecbaba4

During the review of these changes, we put together a document that will eventually be integrated to eng.git or engdoc.git which describes how to configure new dev zones, which you'll likely need in order to build the components covered by this phase of the project (assuming you hadn't set these up for the phase1 integration)

A draft of that document is at:

https://gist.github.com/timfoster/ea8360025e3542080bc175c4f4d7ae31

Of note is the 'Going retro' section - specifically, when you assemble Triton zfs images locally, the platform of the dev zone gets used as the 'min_platform' of the image. The implication of this, is that the Triton instance you're testing with must be at a platform version greater than, or equal to that of your build machine.

By building on devzones running on 'joyent-retro' instances, this restriction is less likely to affect your testing (since our recommended retro image is the same platform image used to perform official builds) While we hope to add a bypass for this restriction eventually via TOOLS-2187, we do also recommend you use caution if employing this bypass.

Please don't hesitate to get in touch if you've any questions or comments. The remaining two phases of this work which we're moving onto next will convert Manta components, and the platform and headnode build over to this framework.

Many thanks again to all the reviewers of this work - your help was very much appreciated!

 tim

Phase 2 components:

  • TRITON-1116 convert sdc-adminui to engbld framework
  • TRITON-1117 convert sdc-amonredis to engbld framework
  • TRITON-1118 convert sdc-assets to engbld framework
  • TRITON-1119 convert sdc-cloud-analytics to engbld framework
  • TRITON-1120 convert sdc-cloudapi to engbld framework
  • TRITON-1121 convert sdc-cnapi to engbld framework
  • TRITON-1122 convert sdc-docker to engbld framework
  • TRITON-1123 convert sdc-fwapi to engbld framework
  • TRITON-1124 convert sdc-manatee to engbld framework
  • TRITON-1125 convert sdc-manta to engbld framework
  • TRITON-1126 convert sdc-napi to engbld framework
  • TRITON-1127 convert sdc-nat to engbld framework
  • TRITON-1128 convert sdc-nfsserver to engbld framework
  • TRITON-1129 convert sdc-portolan to engbld framework
  • TRITON-1130 convert sdc-rabbitmq to engbld framework
  • TRITON-1131 convert sdc-sapi to engbld framework
  • TRITON-1132 convert sdc-sdc to engbld framework
  • TRITON-1133 convert sdc-ufds to engbld framework
  • TRITON-1134 convert sdc-vmapi to engbld framework
  • TRITON-1135 convert sdc-volapi to engbld framework
  • TRITON-1136 convert sdc-workflow to engbld framework
  • TRITON-1137 convert sdcsso to engbld framework
  • TRITON-1138 convert triton-cmon to engbld framework
  • TRITON-1139 convert triton-cns to engbld framework
  • TRITON-1140 convert triton-mockcloud to engbld framework
  • TRITON-1141 convert sdc-agents-core to engbld framework
  • TRITON-1142 convert sdc-agents-installer to engbld framework
  • TRITON-1143 convert sdc-cn-agent to engbld framework
  • TRITON-1144 convert sdc-dockerlogger to engbld framework
  • TRITON-1145 convert sdc-firewaller-agent to engbld framework
  • TRITON-1146 convert sdc-hagfish-watcher to engbld framework
  • TRITON-1147 convert sdc-net-agent to engbld framework
  • TRITON-1148 convert sdc-smart-login to engbld framework
  • TRITON-1149 convert sdc-system-tests to engbld framework
  • TRITON-1150 convert sdc-vm-agent to engbld framework
  • TRITON-1151 convert sdcadm to engbld framework
  • TRITON-1152 convert sdcboot to engbld framework
  • TRITON-1153 convert triton-cmon-agent to engbld framework
  • TOOLS-2171 MG needs to deal with second round of engbld integrations

This flag day message is also available at https://gist.github.com/timfoster/1dc9fb5d8e2fd80e1c94e7987851b42d/edit

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment