This repository has been archived by the owner on Sep 23, 2020. It is now read-only.
/
changelog.html
4039 lines (3873 loc) · 145 KB
/
changelog.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
m4_include(/mcs/m4/worksp.lib.m4)
_NIMBUS_HEADER(Changelog)
_NIMBUS_HEADER2(n,n,n,n,y,n,n)
_NIMBUS_LEFT2_COLUMN
_NIMBUS_LEFT2_ABOUT_SIDEBAR(n,n,n,y)
_NIMBUS_LEFT2_COLUMN_END
_NIMBUS_CENTER2_COLUMN
_NIMBUS_IS_DEPRECATED
<h2>Nimbus Infrastructure Changelog</h2>
<p>For cloud client changes, see
<a href="http://github.com/nimbusproject/nimbus/raw/master/cloud-client/nimbus-cloud-client-src/CHANGES.txt">here.</a>
</p>
<a name="2.8"> </a>
<i>2.8 - Summary</i>
<ul>
<li>
<p>
This release contains many important bug fixes as well as some new features.
</p>
</li>
<li>
<p>
Propagation by means of a file system copy: this can greatly decrease the boot time of VMs on systems where a fast shared file system exists.
</p>
</li>
<li>
<p>
VM image caching: this will greatly increase the boot performance for clouds with a base image that is launched often (a common use case). This works with any propagation method.
</p>
</li>
<li>
<p>
libvirt template support added. A cloud administrator can
now completely control the options sent to libvirt when starting
a virtual machine by editing the template file
</p>
</li>
<li>
<p>
ImportKeyPair is implemented in the EC2 protocols (details below).
</p>
</li>
</ul>
<i>2.8 - IaaS Services</i>
<ul>
<li>
<p>
Internally the Nimbus team has introduced a build and test system
with <a href="http://build.nimbusproject.org">Jenkins</a>.
This has helped us create a more robust and
well tested system as well as making it easier for the community
to make contributions.
</p>
</li>
<li>
<p>
The Nimbus Context Broker has been factored out into a separate tarball install
in addition to being part of the default IaaS installation.
</p>
</li>
<li>
<p>
Implemented EC2 ImportKeyPair operation. The old CreateKeyPair behavior is disabled (the behavior of allowing a "||" token based import mechanism with CreateKeyPair).
</p>
<p>
EC2 used to only have CreateKeyPair, now the EC2 protocols in Nimbus IaaS use ImportKeyPair and CreateKeyPair as intended as operations. The old behavior can be enabled if the administrator wants. (<a href="https://github.com/nimbusproject/nimbus/issues/36">enhancement 36</a>).
</p>
</li>
<li>
<p>
Documentation added to the <a href="http://www.nimbusproject.org/docs/latest/admin/z2c/">zero to cloud guide</a> describing
how to setup Nimbus to work with KVM.
</p>
</li>
<li>
<p>
<i>Bug Fixes</i>
</p>
<ul>
<li>
<p>
<a href="https://github.com/nimbusproject/nimbus/issues/59">ehcache unreliable for critical persistence</a>
</p>
</li>
<li>
<p>
<a href="https://github.com/nimbusproject/nimbus/issues/56">Termination should be retried if there is a fatal issue</a>
</p>
</li>
<li>
<p>
<a href="https://github.com/nimbusproject/nimbus/issues/49">accounting txt file not updated when corrupt VMs expire.</a>
</p>
</li>
<li>
<p>
<a href="https://github.com/nimbusproject/nimbus/issues/48">Add HTTPS unpropagation support.</a>
</p>
</li>
<li>
<p>
<a href="https://github.com/nimbusproject/nimbus/issues/46">Incorrect in_use in nimbus-nodes -l</a>
</p>
</li>
<li>
<p>
<a href="https://github.com/nimbusproject/nimbus/issues/44">User tools have buggy group-authz dir loading</a>
</p>
</li>
<li>
<p>
<a href="https://github.com/nimbusproject/nimbus/issues/37">Needed networks not being respected</a>
</p>
</li>
<li>
<p>
<a href="https://github.com/nimbusproject/nimbus/issues/63">New VM name was limited to a length which was too short in some circumstances</a>
</p>
</li>
<li>
<p>
<a href="https://github.com/nimbusproject/nimbus/issues/59">ehcache unreliable for critical persistence</a>
</p>
</li>
<li>
<p>
<a href="https://github.com/nimbusproject/nimbus/issues/67">Object copy with JetS3t fails</a>
</p>
</li>
<li>
<p>
<a href="https://github.com/nimbusproject/nimbus/issues/52">typica now works with Nimbus Query interface</a>
</p>
</li>
<li>
<p>
<a href="https://github.com/nimbusproject/nimbus/issues/56">Termination is retried if there is a fatal issue</a>
</p>
</li>
<li>
<p>
<a href="https://github.com/nimbusproject/nimbus/issues/65">Safer handling of the gridmap file</a>
</p>
</li>
</ul>
</li>
</ul>
<i>2.8 - LANTorrent</i>
<ul>
<li>
<p>
In this release LANTorrent was repackaged for more pythonic
distribution mechanisms and an important bug was fixed that
caused long term stability problems.
</p>
</li>
<li>
<p>
<i>Bug Fixes</i>
</p>
<ul>
<li>
<p>
<a href="https://github.com/nimbusproject/nimbus/issues/70">Wrong HOME environment variable in LANTorrent's xinetd configuration</a>
</p>
</li>
<li>
<p>
<a href="https://github.com/nimbusproject/nimbus/issues/68">Bugs in the LANTorrent client object fixed. Transfers are more stable.</a>
</p>
</li>
<li>
<p>
<a href="https://github.com/nimbusproject/nimbus/issues/39">Lantorrent runaway after killing a newly created VM</a>
</p>
</li>
<li>
<p>
<a href="https://github.com/nimbusproject/nimbus/issues/57">LANTorrent can't be installed without an Internet connection</a>
</p>
</li>
<li>
<p>
<a href="https://github.com/nimbusproject/nimbus/issues/51">Add lantorrent tests to test suite.</a>
</p>
</li>
<li>
<p>
<a href="https://github.com/nimbusproject/nimbus/issues/32">Pilot updates</a>
</p>
</li>
</ul>
</li>
</ul>
<i>2.8 - Control Agents</i>
<ul>
<li>
<p>
libvirt template support added. A cloud administrator can
now completely control the options sent to libvirt when starting
a virtual machine by editing the template file
<tt class="literal">/opt/nimbus/etc/workspace-control/libvirt_template.xml</tt>
on the VMM nodes.
</p>
</li>
<li>
<p>
A cache of propagated images can now be kept on each VMM. Before
an image is propagated the cache is checked for an image with a
matching checksum. If found that image is used and no propagation
is needed which can save a significant amount of time. This will
work with any propagation mechanism.
</p>
</li>
<li>
<p>
The cp (copy) propagation driver has been introduced in this release.
This prepares an image for use by a VMM by copying it directly out
of the Cumulus data store and into a temporary location from which it
will be booted. For users with shared fast file systems this can
bring great performance benefits.
</p>
</li>
<li>
<p>
<i>Bug Fixes</i>
</p>
<ul>
<li>
<p>
<a href="https://github.com/nimbusproject/nimbus/issues/33">virtio support in generated libvirt xml</a>
</p>
</li>
<li>
<p>
<a href="https://github.com/nimbusproject/nimbus/issues/55">Workspace control verifies old unpropagation URL when saving with a new name</a>
</p>
</li>
</ul>
</li>
</ul>
<i>2.8 - Additional Notes</i>
<ul>
<li>
<p>
List of
<a href="http://github.com/nimbusproject/nimbus/compare/nimbus-release-2.7...nimbus-release-2.8">all
commits</a>
between Nimbus 2.7 final and Nimbus 2.8 final.
</p>
</li>
</ul>
<a name="2.7"> </a>
<br><hr><br>
<i>2.7 - Summary</i>
<ul>
<li>
<p>
Support for backfill and spot VM instances was introduced. Backfill instances are configured by the
administrator and automatically start on idle resources. When user requests are received, backfill
instances are preempted and terminated.
</p>
<p>
Spot instances are similar to backfill, but are initiated by the user. Users may "bid" on VM slots and
compete for available resources. Like backfill, spot instances can be preempted and terminated at any
time. Preemption occurs when either a real (non-spot) request or a spot request with a higher bid is
received and no other resources are available.
</p>
</li>
<li>
<p>
The EC2 Query interface has substantially improved compatibility with EC2 clients. The generated XML
is now largely identical.
</p>
</li>
<li>
<p>
Idempotent instance creation is now supported, via the EC2 interfaces.
</p>
</li>
<li>
<p>
There are also numerous bug fixes and minor enhancements.
</p>
</li>
</ul>
<i>2.7 - IaaS Services</i>
<ul>
<li>
<p>
Support for backfill and spot VM instances was introduced.
See the <a href="admin/reference.html#backfill-and-spot-instances">documentation</a> for more information.
</p>
</li>
<li>
<p>
Idempotent instance creation is now supported, via the EC2 interfaces.
</p>
</li>
<li>
<p>
The metadata server now supports listening on multiple network interfaces. The URL provided to
VMs can be configured based on the requested networks.
</p>
</li>
<li>
<p>
The EC2 Query interface has substantially improved compatibility with EC2 clients. The generated XML
is now largely identical. The name space version in responses matches the request version
regardless of the actual version. Additionally, version 1 signatures are now supported, to enable
some clients that never updated to version 2.
</p>
</li>
<li>
<p>
The <tt class="literal">scripts/check-dependencies.sh</tt> program has been added to the services
installer to help detect dependency problems before starting the installation process.
</p>
</li>
<li>
<p>
Added support for specifying multiple CPU architectures in <tt class="literal">vmm.conf</tt>. Detailed in
<a href="https://github.com/nimbusproject/nimbus/issues/closed#issue/15">issue 15</a>.
</p>
</li>
<li>
<p>
<i>Bug Fixes</i>
</p>
<ul>
<li>
<p>
<a href="https://github.com/nimbusproject/nimbus/issues/closed#issue/27">Fixed bug with user-selected kernels in workspace-control</a>
</p>
</li>
<li>
<p>
<a href="https://github.com/nimbusproject/nimbus/issues/issue/25">Fixed bug in nimbus-edit-user regarding group management</a>
</p>
</li>
<li>
<p>
<a href="https://github.com/nimbusproject/nimbus/issues/closed#issue/7">Fix unpropagation exception in lantorrent</a>
</p>
</li>
<li>
<p>
<a href="https://github.com/nimbusproject/nimbus/issues/closed/#issue/9">Allow metadata server queries to use "/latest/"</a>
</p>
</li>
<li>
<p>
<a href="https://github.com/nimbusproject/nimbus/issues/closed/#issue/10">nimbus-remove-user --help dumps stack</a>
</p>
</li>
<li>
<p>
<a href="https://github.com/nimbusproject/nimbus/issues/closed/#issue/13">Installer broken with Python 2.7.1</a>
</p>
</li>
<li>
<p>
<a href="https://github.com/nimbusproject/nimbus/issues/closed/#issue/17">Nimbus EC2 Query interface should support signature version 1</a>
</p>
</li>
<li>
<p>
<a href="https://github.com/nimbusproject/nimbus/issues/closed/#issue/19">Query interface generated XML isn't identical (enough) to EC2</a>
</p>
</li>
<li>
<p>
<a href="https://github.com/nimbusproject/nimbus/issues/closed/#issue/20">nimbus-reset-state not sourcing virtual env</a>
</p>
</li>
<li>
<p>
<a href="https://github.com/nimbusproject/nimbus/issues/closed/#issue/21">EC2 query interface parameter lists break on POST requests</a>
</p>
</li>
<li>
<p>
<a href="https://github.com/nimbusproject/nimbus/issues/closed/#issue/22">cache mechanism not surviving restarts</a>
</p>
</li>
<li>
<p>
<a href="https://bugzilla.mcs.anl.gov/globus/show_bug.cgi?id=7097">nimbus-new-user doesn't accept relative paths</a>
</p>
</li>
</ul>
</li>
</ul>
<i>2.7 - LANTorrent</i>
<ul>
<li>
<p>
Improved logging output.
</p>
</li>
<li>
<p>
Added checksum checks to the data as it is streaming. Peers report back their values and errors are
thrown for all non-matching cases.
</p>
</li>
<li>
<p>
Altered the use of nonblocking sockets to have a more efficient process.
</p>
</li>
<li>
<p>
<i>Bug Fixes</i>
</p>
<ul>
<li>
<p>
<a href="https://github.com/nimbusproject/nimbus/issues/closed#issue/24">LANTorrent transfers don't correctly check the result of send()</a>
</p>
</li>
</ul>
</li>
</ul>
<i>2.7 - Control Agents</i>
<ul>
<li>
<p>
Added support for propagation from an HTTPS server with X509 proxy authentication. See
<a href="https://github.com/nimbusproject/nimbus/issues/closed/#issue/12">issue 12</a> for
details.
</p>
</li>
<li>
<p>
<i>Bug Fixes</i>
</p>
<ul>
<li>
<p>
<a href="https://github.com/nimbusproject/nimbus/issues/closed/#issue/18">mount-alter.sh terminating without umount</a>
</p>
</li>
<li>
<p>
<a href="https://github.com/nimbusproject/nimbus/issues/closed/#issue/14">Add Locking to workspace pilot</a>
</p>
</li>
<li>
<p>
<a href="https://github.com/nimbusproject/nimbus/issues/closed#issue/23">Gzipped images cannot be restarted</a>
</p>
</li>
<li>
<p>
<a href="https://github.com/nimbusproject/nimbus/issues/issue/27">User-selected kernels broken in workspace-control</a>
</p>
</li>
</ul>
</li>
</ul>
<i>2.7 - Additional Notes</i>
<ul>
<li>
<p>
List of
<a href="http://github.com/nimbusproject/nimbus/compare/nimbus-release-2.6...nimbus-release-2.7">all
commits</a>
between Nimbus 2.6 final and Nimbus 2.7 final.
</p>
</li>
</ul>
<a name="2.6"> </a>
<br><hr><br>
<i>2.6 - Summary</i>
<ul>
<li>
<p>
This is the first release of LANTorrent, a fast multicast file distribution protocol designed to saturate all the links in a switch. This works best for situations with a local area network, large files, and many cooperative peers that need the same file -- i.e., it is geared towards IaaS image propagation (but could work in other scenarios).
</p>
</li>
<li>
<p>
Dynamic VMM configuration management is now possible with the new <tt class="literal">nimbus-nodes</tt> program. This allows you to adjust the resource pool while the service is still running, adding and removing resources on the fly.
</p>
</li>
<li>
<p>
The context broker has a new client-side HTTP/REST interface in addition to WSRF. Users authenticate with the same tokens they use for Cumulus and the Elastic Query API. This opens up the context broker for several new client integrations including ones using alternate languages.
</p>
</li>
<li>
<p>
Cumulus now supports the S3 COPY operation.
</p>
</li>
<li>
<p>
A new upgrade tool is introduced, <tt class="literal">install-from</tt>. This assists with updating a previous Nimbus installations (2.5 and higher). It currently requires that the old Nimbus services are all stopped and no VMs are deployed.
</p>
</li>
<li>
<p>
<tt class="literal">nimbus-import-users</tt> is a new program that allows multiple cloud installations to coordinate user information with each other.
</p>
</li>
<li>
<p>
<tt class="literal">nimbus-public-image</tt> is a new program that allows administrators to register VM images in the local Cumulus repository that will be usable for all users of the system (but of course only stored once on disk).
</p>
</li>
<li>
<p>
As usual, some bug fixes and minor enhancements.
</p>
</li>
</ul>
<i>2.6 - Installer</i>
<ul>
<li>
<p>
<i>install-from program</i>
</p>
<p>
A new upgrade tool is introduced, this assists with updating a previous Nimbus installations (2.5 and higher). It currently requires that the old Nimbus services are all stopped and no VMs are deployed.
</p>
<p>
You use this program instead of the regular <tt class="literal">install</tt> instructions. Most of the installation process is exactly as normal, but <tt class="literal">install-from</tt> will base most of the initial configurations on your old installation.
</p>
<p>
It is not yet entirely Magic™ so you will need to follow the instructions in the <a href="admin/upgrading.html">upgrade guide</a> to make it happen.
</p>
</li>
</ul>
<i>2.6 - IaaS Services</i>
<ul>
<li>
<p>
<i>nimbus-nodes program</i>
</p>
<p>
Dynamic VMM configuration management is now possible with the new <tt class="literal">nimbus-nodes</tt> program. This allows you to adjust the resource pool while the service is still running, adding and removing resources on the fly.
</p>
<p>
For information and instructions, see <a href="admin/reference.html#resource-pool">this section</a> of the administrator guide.
</p>
</li>
<li>
<p>
<i>nimbus-import-users</i>
</p>
<p>
This is a new program that allows multiple cloud installations to coordinate user information with each other.
</p>
<p>
You can "dump" user information into a text file and this allows you to import it elsewhere. This allows administrators (or larger groups) to coordinate users across clusters/installations.
</p>
<p>
It is compatible with the <tt class="literal">nimbus-list-users</tt> tool, you can for example run things like <tt class="literal">ssh nimbus@othercloud nimbus-list-users % | nimbus-import-users</tt>
</p>
</li>
<li>
<p>
<i>nimbus-public-image</i>
</p>
<p>
This is a new program that allows administrators to register VM images in the local Cumulus repository that will be usable for all users of the system.
</p>
<p>
These are read-only images that all Nimbus users will see as an option in their "--list" output for running.
</p>
<p>
To save these images as new, derivative templates, the user would need to run "--save --new-name" and create a new object.
</p>
</li>
<li>
<p>
<i>Passthrough configuration</i>
</p>
<p>
When an image file URL scheme is not the normal "cumulus://", previously the service would always pass this along to the VMM to interpret on its own.
</p>
<p>
Now you can explicitly set what propagation to use for "cumulus://" and what passthrough schemes are allowed (if any).
</p>
<p>
Enhancement <a href="http://bugzilla.mcs.anl.gov/globus/show_bug.cgi?id=7092">7092</a>
shows where to find the configuration.
</p>
</li>
<li>
<p>
<i>Bug Fixes</i>
</p>
<ul>
<li>
<p>
<a href="http://bugzilla.mcs.anl.gov/globus/show_bug.cgi?id=7084">Bug 7084 - Explicit MAC->IP mappings are ignored after service restart</a>
</p>
</li>
<li>
<p>
<a href="http://bugzilla.mcs.anl.gov/globus/show_bug.cgi?id=7088">Bug 7088 - newname/alternative unpropagated target fails</a>
</p>
</li>
<li>
<p>
<a href="http://bugzilla.mcs.anl.gov/globus/show_bug.cgi?id=7096">Bug 7096 - User mgmt tools group number validation is excessive</a>
</p>
</li>
</ul>
</li>
</ul>
<i>2.6 - Cumulus</i>
<ul>
<li>
<p>
<i>COPY</i>
</p>
<p>
The <a href="http://docs.amazonwebservices.com/AmazonS3/2006-03-01/index.html?UsingCopyingObjects.html">COPY</a>
operation allows you to duplicate an object stored in the system without having to do any data transfer to your client machine.
</p>
<p>
It was tested with <tt class="literal">s3cmd</tt> and <tt class="literal">boto</tt>. Future cloud-client versions could use this more natively for image duplication/rename.
</p>
</li>
<li>
<p>
<i>Redirection</i>
</p>
<p>
In order to make Cumulus a scalable service we added a feature
which takes advantage of the temporary redirection in error in
the
<a href="http://docs.amazonwebservices.com/AmazonS3/latest/index.html">Amazon S3 Protocol</a>. A Cumulus administrator can create a text file
full of cloned Cumulus server contact strings. A maximum number
of allowed connected clients is associated with each replicated
Cumulus server. If, after a client connects and authenticates,
that number is exceeded, then a <i>301 Temporary Redirect</i>
error is return to the client instructing it to try a different
Cumulus server.
</p>
</li>
<li>
<p>
<i>Postgres DB for Authentication</i>
</p>
<p>
Minor changes were made to the service to allow an admin to
configure Cumulus so that it will use postgres instead of the
default SQLite DB.
</p>
</li>
<li>
<p>
<i>Bug Fixes</i>
</p>
<ul>
<li>
<p>
<a href="http://bugzilla.mcs.anl.gov/globus/show_bug.cgi?id=7083">Bug 7083 - s3cmd setacl public fails</a>
</p>
</li>
</ul>
</ul>
</ul>
<i>2.6 - LANTorrent</i>
<ul>
<li>
<p>
<i>Introducing LANTorrent!</i>
</p>
<p>
This is the first release of LANTorrent, a fast multicast file distribution protocol designed to saturate all the links in a switch.
</p>
<p>
This works best for situations with a local area network, large files, and many cooperative peers that need the same file -- i.e., it is geared towards IaaS image propagation (but could work in other scenarios).
</p>
<p>
It is disabled by default and takes extra steps to activate. See
<a href="admin/reference.html#lantorrent">this section</a> of
the administrator's guide for instructions as well as
<a href="admin/reference.html#lantorrent-protocol">detailed explanations</a> of how it works.
</p>
</li>
</ul>
<i>2.6 - Context Broker</i>
<ul>
<li>
<p>
<i>HTTP/REST support</i>
</p>
<p>
The context broker has a new client-side HTTP/REST interface in addition to WSRF. Users authenticate with the same tokens they use for Cumulus and the Elastic Query API. This opens up the context broker for several new client integrations including ones using alternate languages.
</p>
<p>
For example there is a
<a href="http://github.com/nimbusproject/Nimboss">prototype
client api</a> being built that integrates with the REST broker.
</p>
</li>
</ul>
<i>2.6 - Control Agents</i>
<ul>
<li>
Support for LANTorrent (see above). The relevant configurations are
in the "propagation.conf" file.
</li>
<li>
<p>
<i>Bug Fixes</i>
</p>
<ul>
<li>
<p>
<a href="http://bugzilla.mcs.anl.gov/globus/show_bug.cgi?id=7101">Bug 7101 - dhcp-config.sh is unreliable on shared filesystem</a>
</p>
</li>
</ul>
</li>
</ul>
<i>2.6 - Cloud Client</i>
<ul>
<li>
<p>
<i>Use cloud-client 16 or higher</i>
</p>
<p>
As of this release, the latest cloud client is
<a href="http://github.com/nimbusproject/nimbus/raw/master/cloud-client/nimbus-cloud-client-src/CHANGES.txt">number
17</a>. Cloud client 16 will also work, but 15 or before will not
due to the introduction of Cumulus in Nimbus 2.5.
</p>
</li>
</ul>
<i>2.6 - Additional Notes</i>
<ul>
<li>
<p>
List of
<a href="http://github.com/nimbusproject/nimbus/compare/nimbus-release-2.5...nimbus-release-2.6">all
commits</a>
between Nimbus 2.5 final and 2.6 final.
</p>
</li>
<li>
<p>
Problems addressed in RC2 vs. RC1
(<a href="http://github.com/nimbusproject/nimbus/compare/nimbus-release-2.6-RC1...nimbus-release-2.6-RC2">All commits</a>)
</p>
<ul>
<li>
<p>
Issue with image md5sums not getting recorded in certain situations.
</p>
</li>
<li>
<p>
Ran into situations where two seconds was not enough time to get a database connection from a pool of connections. Decided to make this infinite (for correctness purposes, the timeouts are not handled correctly).
</p>
</li>
<li>
<p>
The "bad CPU architecture" remote error message was incorrectly stated.
</p>
</li>
<li>
<p>
The build and test suite runs on more platforms now by using the /tmp directory for special files.
</p>
</li>
<li>
<p>
Service support for the new admin client "nimbus-nodes" did not handle a missing configuration gracefully.
</p>
</li>
<li>
<p>
Cumulus includes a new scalability test.
</p>
</li>
<li>
<p>
The installer did not handle the lack of the "uuidgen"
command well, using a library instead of relying on that
commandline being there.
</p>
</li>
<li>
<p>
The service was giving a bad error message for image URL schemes (besides 'file' or 'cumulus') that were not explicitly authorized.
</p>
</li>
</ul>
</li>
</ul>
<a name="2.5"> </a>
<br><hr><br>
<i>2.5 - Summary</i>
<ul>
<li>
<p>
<i>We are happy to announce the first version of Cumulus!</i>
</p>
<p>
Cumulus is a storage cloud implementation compatible with the Amazon Web Services S3 REST API (with small exceptions), it works seamlessly with S3 clients such as s3cmd, jets3t, and boto. In addition, it offers extra functionality such as disk quota enforcement.
</p>
<p>
Cumulus replaces the current GridFTP-based upload and download of VM images: it integrates tightly in a Nimbus installation as the VM image repository solution. And it can be also installed on its own to manage a storage cloud: a Nimbus IaaS installation needs Cumulus but not vice versa.
</p>
<p>
Read more below in the Cumulus section of the changelog.
</p>
</li>
<li>
<p>
<i>Zero To Cloud installation process</i>
</p>
<p>
Besides being the first Cumulus release, the other major event of 2.5 is the first release of the "Zero To Cloud" installation process.
</p>
<p>
Many of the new programs and enhancements in this release work together with the goal of providing a seamless installation process. Read more in the changelog below about each new feature, highlights include:
</p>
<ul>
<li>
<p>
A new user management system: users can be added and managed quickly. Their credentials are created on the fly (but there is still an alternative path for coexistence with your own credential system).
</p>
</li>
<li>
<p>
All of the new user management tools include a machine parsable mode that makes them easy to incorporate into your own scripts.
</p>
</li>
<li>
<p>
Tight user integration with Cumulus: user management includes user setup with the image repository as well as the IaaS services.
</p>
</li>
<li>
<p>
Tight integration between the user management tools and the web application. This allows administrators to add a user and instantly receive the secure URL that the new user will visit to pick up his credentials and cloud.properties file.
</p>
</li>
<li>
<p>
No unix account separation or root account needed for Cumulus -- installation is easier because the IaaS central services and Cumulus can live in the same, non-root unix account.
</p>
</li>
<li>
<p>
The IaaS services are able to consult information in a database about files the remote user wants to launch. When the "outside" namespace of the file is Cumulus based, there is a translation to an "inside" location and mechanism. This technique is now used to encapsulate propagation mechanisms, allowing for an easy way to introduce new and faster methods.
</p>
</li>
</ul>
<p>
All of this combined to allow us to, among other things, provide a new installation process for Nimbus. You can now tend to the central service node installation separately and very quickly. Further, you install in a "fake" mode that doesn't actually invoke hypervisor machines yet. Doing all of this allows you to know that the central services are configured and working (including security), leaving VMM related matters to be tackled separately.
</p>
</li>
<li>
<p>
<i>Integration with a central, site DHCPd</i>
</p>
<p>
Instead of hosting a private DHPCd for each VMM, Nimbus now supports (by default) editing a lease file for a central DHCPd on the LAN. This makes it easier to install and integrate with existing infrastructure. The old method is supported as an advanced configuration. Details below in the IaaS Services and workspace-control sections.
</p>
</li>
<li>
<p>
<i>New scheduling options</i>
</p>
<p>
When using the default scheduler, the VMM selection process is now more configurable:
</p>
<p>
There is a <i>round-robin</i> configuration that looks for available nodes with the highest percentage of free RAM. And a <i>greedy</i> configuration that looks for available nodes with the lowest percentage of free RAM. Details below.
</p>
</li>
<li>
<p>
<i>New options for pilot based scheduling</i>
</p>
<p>
The pilot module now sends more information to the local resource manager (such as Torque). This is for accounting and potentially authorization purposes, you can now more easily track remote users and more information about the launch via the resource manager itself.
</p>
</li>
<li>
<p>
<i>New alternative propagation methods</i>
</p>
<p>
There are two new contributed propagation drivers for getting VM images to the hypervisor nodes: HTTP and HDFS. These are for use outside of the cloud client currently, and you need to configure Nimbus to allow for non-Cumulus-based image locations.
</p>
<p>
These are for use on sites where the remote user knows more about image locations than the Cumulus name for it. The HTTP driver is also good for having a central image repository (you can specify trusted hosts to pull from).
</p>
</li>
<li>
<p>
<i>Better performing blankspace: physical partition leases</i>
</p>
<p>
In order to support very large temporary space partitions for VMs, and fast access to them, Nimbus now allows you to configure a list of physical partitions to lease out to incoming Nimbus VMs on each node (formatted for each use).
</p>
</li>
<li>
<p>
<i>Support for user-requested number of cores</i>
</p>
<p>
Nimbus now allows remote users to specify the number of cores the VM(s) should have. The authorization policies now support this as well, allowing administrators to specify the maximum allowed for each user/group.
</p>
</li>
<li>
<p>
<i>New service node dependency requirements</i>
</p>
<p>
See the Cumulus section for specifics.
</p>
</li>
<li>
<p>
<i>Bug fixes and smaller enhancements</i>
</p>
<p>
See each section below for specifics.
</p>
</li>
<li>
<p>
<i>For developers</i>
</p>
<p>
Highlights for software developers include a new internal testing
framework for the RM API, tight integration with IntelliJ IDEA if
you use that IDE, a propagate-only mode (no VMM required), a way to
quickly overwrite just jar files in an installation, and better
tarball/release management.
</p>
</li>
</ul>
<i>2.5 - Installer</i>
<ul>
<li>
<p>
<i>Zero To Cloud Guide</i>
</p>
<p>
You can now follow <a href="admin/z2c/index.html">one installation document</a> step by step and achieve a setup that works for the cloud-client program.
</p>
</li>
<li>
<p>
Now installs and configures Cumulus.