defaria.com/blogs/Status/archives/000697.html

   1 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
   2    "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
   3 <html xmlns="http://www.w3.org/1999/xhtml" id="sixapart-standard">
   4 <head>
   5    <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
   6    <meta name="generator" content="Movable Type 5.2.3" />
   7
   8    <link rel="stylesheet" href="http://defaria.com/blogs/Status/styles-site.css" type="text/css" />
   9    <link rel="alternate" type="application/atom+xml" title="Atom" href="http://defaria.com/blogs/Status/atom.xml" />
  10    <link rel="alternate" type="application/rss+xml" title="RSS 2.0" href="http://defaria.com/blogs/Status/index.xml" />
  11
  12    <title>Status for Andrew DeFaria: For immediate release</title>
  13
  14    <link rel="start" href="http://defaria.com/blogs/Status/" title="Home" />
  15    <link rel="prev" href="http://defaria.com/blogs/Status/archives/000696.html" title="Rexec" />
  16    <link rel="next" href="http://defaria.com/blogs/Status/archives/000698.html" title="New easter options" />
  17
  18    <!--
  19 <rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
  20          xmlns:trackback="http://madskills.com/public/xml/rss/module/trackback/"
  21          xmlns:dc="http://purl.org/dc/elements/1.1/">
  22 <rdf:Description
  23     rdf:about="http://defaria.com/blogs/Status/archives/000697.html"
  24     trackback:ping="http://defaria.com/mt/mt-tb.cgi/84"
  25     dc:title="For immediate release"
  26     dc:identifier="http://defaria.com/blogs/Status/archives/000697.html"
  27     dc:subject="General Dynamics"
  28     dc:description="For immediate release... Recently Gantry mentioned the following problem: Error Prone Deliveries: Another problem is that Reinaldo&apos;s private files have to be merged manually. Ross, Andrew, and I are in a similar situation now where we have to take a..."
  29     dc:creator=""
  30     dc:date="2008-02-20T14:49:49-06:00" />
  31 </rdf:RDF>
  32 -->
  33
  34
  35
  36
  37    <script type="text/javascript" src="http://defaria.com/blogs/Status/mt-site.js"></script>
  38 </head>
  39 <body class="layout-one-column" onload="individualArchivesOnLoad(commenter_name)">
  40    <div id="container">
  41       <div id="container-inner" class="pkg">
  42
  43          <div id="banner">
  44             <div id="banner-inner" class="pkg">
  45                <h1 id="banner-header"><a href="http://defaria.com/blogs/Status/" accesskey="1">Status for Andrew DeFaria</a></h1>
  46                <h2 id="banner-description">Searchable status reports and work log</h2>
  47             </div>
  48          </div>
  49
  50          <div id="pagebody">
  51             <div id="pagebody-inner" class="pkg">
  52                <div id="alpha">
  53                   <div id="alpha-inner" class="pkg">
  54
  55                      <p class="content-nav">
  56                         <a href="http://defaria.com/blogs/Status/archives/000696.html">&laquo; Rexec</a> |
  57                         <a href="http://defaria.com/blogs/Status/">Main</a>
  58                         | <a href="http://defaria.com/blogs/Status/archives/000698.html">New easter options &raquo;</a>
  59                      </p>
  60
  61                      <a id="a000697"></a>
  62                      <div class="entry" id="entry-697">
  63                         <h3 class="entry-header">For immediate release</h3>
  64                         <div class="entry-content">
  65                            <div class="entry-body">
  66                               <h2>For immediate release...</h2>
  67
  68 <p>Recently Gantry mentioned the following problem:</p>
  69
  70 <blockquote type=cite>
  71   <p>Error Prone Deliveries:</p>
  72
  73   <p>Another problem is that Reinaldo's private files have to be merged
  74 manually.</p>
  75
  76   <p>Ross, Andrew, and I are in a similar situation now where we have to
  77 take a snapshot of directories in a view over to seast1 in order to do
  78 development, then remember what we changed and copy them back in and
  79 deliver.</p>
  80
  81   <p>We have already made several mistakes. </p>
  82 </blockquote>
  83
  84 <p>The problem here is that we have two different Clearcase registry
  85 regions and subnets, code is developed in one region and run in the
  86 other. Gantry proposed a solution of writing more script to maintain
  87 that will essentially copy things between systems. I would like to
  88 propose an alternative...</p>
  89
  90 <h2>Release process</h2>
  91
  92 <p>What if we instead had a release process such that we deliver our
  93 development to the feature stream that is then automatically seen over
  94 on the cclinux region? Code is developed through the WOR process on the
  95 RAN and delivered to the feature stream. This stream has an official
  96 view which is exported to the cclinux region where it is mounted
  97 directly into place<a href="#note_1"><sup>1</sup></a>. Since all
  98 processes that utilize these scripts do so through this base they are
  99 all automatically and immediately updated when the view is updated.
 100 Additionally code is developed cognizant of this base such that an
 101 alternate base can easily be set allowing one to test the release
 102 before making it official.</p>
 103
 104 <h2>Solution proposed</h2>
 105
 106 <h3>Exporting a view</h3>
 107
 108 <p>Clearcase has the ability to export a view/vob path from a view
 109 server to any other machine. This allows you to "access Clearcase from
 110 a machine which does not have Clearcase" (see ct man export_mvfs). In
 111 order to do this a systems administrator adds a line to
 112 /etc/exports.mvfs on the view server where the view resides using the
 113 format of:</p>
 114
 115 <div class=code><pre>
 116 /view/&lt;<i>view_name</i>&gt;/vobs/&lt;<i>vobpath</i>&gt;&lt;<i>netgroup or machine</i>&gt;
 117 </pre></div>
 118
 119 <p>And executes the /opt/rational/clearcase/etc/export_mvfs -a
 120 command.  Additionally &lt;<i>view_name</i>&gt; should be started<a
 121 href="#note_2"><sup>2</sup></a>.</p>
 122
 123 <h3>Official view</h3>
 124
 125 <p>Additionally, as noted above, a view must be utilized. I suggest using
 126 what I like to call <i>official views</i> for this. An <i>official
 127 view</i> is merely a view not associated with any particular person
 128 (e.g. maybe ccadm) that serves in an official capacity. This view
 129 usually has a simple config spec such as the following:</p>
 130
 131 <div class=code><pre>
 132 element * REL_1.0 -nocheckout
 133 </pre></div>
 134
 135 <p>thereby limiting what was seen through the view as only that which is
 136 labeled with REL_1.0. The release process therefore consisted of
 137 applying the REL_1.0 label and poof! Automatically and immediately the
 138 new version was available. Updating to say a REL_1.1 release would
 139 involve then simply a ct setcs and a changing of REL_1.0 to REL_1.1.</p>
 140
 141 <p>For UCM based views, translate the above to applicable baselines...</p>
 142
 143 <h3>Importing the view</h3>
 144
 145 <p>On the client machine, importing the view is simply a mount
 146 command.  The suggestion here is to mount directly to our base,
 147 /usr/local/east:</p>
 148
 149 <div class=code><pre>
 150 $ mount view1:/views/&lt;<i>official view</i>&gt;/vobs/rantest /usr/local/east
 151 </pre></div>
 152
 153 <p>(Actually this should be added to /etc/fstab for automatic, at boot
 154 time, mounting).</p>
 155
 156 <h3>Security and visibility</h3>
 157
 158 <p>There is concern regarding exposing too much visibility of vob
 159 elements in the cclinux region. Since /etc/exports.mvfs allows us to
 160 specify an exacting path of what is exported we can insure that we are
 161 only exporting the .../vobs/rantest portion or even a subdirectory(s)
 162 under rantest. This should sufficiently limit the scope of what's
 163 exposed.</p>
 164
 165 <h2>Notes</h2>
 166
 167 <ol>
 168   <li><small><a name="note_1"></a>This assumes that we adopt a concept
 169 of a base variable from which everything emanates (e.g. /usr/local/east)</small></li>
 170   <li><small><a name="note_2"></a>At HP I devised a simply script
 171 solution to insure that views listed in /etc/views_to_start would be
 172 started at boot up on the view servers.</small></li>
 173 </ol>
 174
 175 <p>Comments? Concerns?</p>
 176                            </div>
 177                            <div id="more" class="entry-more">
 178
 179                            </div>
 180                         </div>
 181                         <p class="entry-footer">
 182                            <span class="post-footers">Posted by  on February 20, 2008  2:49 PM</span> <span class="separator">|</span> <a class="permalink" href="http://defaria.com/blogs/Status/archives/000697.html">Permalink</a>
 183                         </p>
 184                      </div>
 185
 186
 187                      <div class="trackbacks">
 188                         <h3 id="trackback" class="trackbacks-header">TrackBack</h3>
 189                         <div id="trackbacks-info">
 190                            <p>TrackBack URL for this entry:<br />http://defaria.com/mt/mt-tb.cgi/84</p>
 191                         </div>
 192                         <div class="trackbacks-content">
 193
 194                         </div>
 195                      </div>
 196
 197
 198
 199                   </div>
 200                </div>
 201             </div>
 202          </div>
 203       </div>
 204    </div>
 205 </body>
 206 </html>