udaykiran19491/user-stories-from-tawos-for-llm-fine-tuning huggingface dataset:
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "Scott from New River Kinematics visited for 3 days.    Wednesday, we had a long meeting with Sandrine to discuss ASC development, and Scott and I worked on addressing bugs and unclear elements of the implementation of the API.    Thursday we had the hands on test, which was successful. We had the alignment model on my laptop, driving T2SA on a windows host, which in turn talked to the physical laser tracker. We are able to control the laser tracker and measure a scaled-down model  of the full telescope through the AlignmentModel python class. We can get calculate offsets from the desired position in either the M1M3 coordinate space, or local coordinates for M2, Camera, or anything else that is designated in the template. We can script commands together to accomplish a series of actions, which can essentially be copy/pasted to build the CSC logic. We also identified several new API commands we want to add, including the option of calculating single-point offsets between any two points.    Friday, we started implementing changes and new commands we came up with the previous day. Also briefly discussed collaborating on a paper on the measurement techniques used in the alignment system to submit to a metrology conference this summer. "
Answer: 111.0

User story: "Prep work for visit from Scott Sandwith at New River Kinematics. Includes    -Resolve issues with latest build of T2SA, which was not connecting to SA properly    -Add support in model class for recent additions and changes to the API    -Assemble a jupyter notebook that allows us to script commands to T2SA"
Answer: 125.0

User story: "It seems like ATDome is mixing in position with not in position.           "
Answer: 30462.0

User story: "the command {{make_idl_files.py all}} is broken after upgrade to ts_xml 4.6. I think it is due to the fact that is uses an entry that was removed from the xml file. "
Answer: 20128.0

User story: "In addition to creating a Jenkins file for building the deployment container, get a conda package build Jenkins file made as well."
Answer: 39499.0

User story: "Update the deployment scripts for AT services"
Answer: 34783.0

User story: "Based on the cert-manager documentation, there's no need to have separate issuers for every namespace in Roundtable since we want to use the same basic configuration (email address, solver, and so forth) for all certificates.    Switch Roundtable to a single ClusterIssuer instead, and remove all the redundant Issuer resources."
Answer: 9686.0

User story: "Despite being a member of the Data Management team in the lsst GitHub org, I don't have access to nublado.lsst.codes. After GitHub authentication I get a 403 : Forbidden error."
Answer: 1073.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: In DM-23490 the plate scale of LATISS was changed but the tests were not run before merging. This is breaking master:    {code}  self = <test_generateCamera.PhosimToRaftsTestCase testMethod=testGenerateCameraLatiss>      def testGenerateCameraLatiss(self):          """Test with LATISS in a test directory."""          content = self.runGenerateCamera(["latiss", "lsstCam", os.path.curdir])          self.assertEqual(content["name"], "LATISS")  >       self.assertEqual(content["plateScale"], 20.0)  E       AssertionError: 10.112 != 20.0  {code}    I will fix the plate scale in the tests.
Answer: 185.0

User story: "Update the GitHub repository name, top-level Python package, documentation, Docker image, and Kubernetes deployment name accordingly. Ensure the GitHub description says that it is an identity mapper currently supporting GitHub and Slack."
Answer: 9053.0

User story: "New version of header service needs a container to run on the summit asap.    "
Answer: 1.0

User story: It was noted today that files in the ci_hsc_gen3 datastore are not unique and instead look like {{DATA/raw/hsc/raw/i/HSC-I/903986/raw_i_HSC-I_903986_903986_22_HSC_raw/hsc.fits}} -- this is because "run" has a value of {{raw/hsc}} and "run" is at the end of the template.    The templating system should replace / with _. Optionally we could also introduce a "/" format modifier to allow "/" to be retained.
Answer: 1081.0

User story: "Besides powering off this VM, this will likely involve:   * redirecting the DNS to the new {{lsst-dtnXX}} hosts   * updating documentation (e.g. developer.lsst.io )   * cleaning up monitoring"
Answer: 48753.0

User story: "xcat provisioning was changed to remove nfs rpms if nodes are not using them. Puppet is then responsible for reinstalling the nfs rpms.    Jake created a profile to facilitate this, but it needs to be added to the k8s role manifests."
Answer: 31.0

User story: "Debugging dispatching validate_drp metrics during https://jira.lsstcorp.org/browse/DM-23121  has added junk to our squash dashboard:    https://chronograf-demo.lsst.codes/sources/2/dashboards/53?tempVars%5BFilter%5D=HSC-R&tempVars%5Bdataset%5D=_internal&lower=2019-09-02T20%3A43%3A00.000Z&upper=2020-04-07T20%3A43%3A00.000Z     I'd think that deleting everything after Sept and re-dispatching would be easiest, but I'll defer to you and [~<USER> on the best way to clean this up."
Answer: 1321.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "In the first implementation of the EFD deployment in Argo CD namespaces were configured in the parent app, all secrets in the  {{vault-secrets-operator}} app and the ingress configuration for some of the apps was configured in the {{nginx-ingress}} app.     That created a problem when we did the NCSA test stand EFD deployment. In that deployment, the {{nginx-ingress}} app was not needed because the ingress controller was already present in the cluster. However, we still needed the ingress rules deployed as part of the {{nginx-ingress}} app. A temporary solution was to create another Argo CD parent app for the NCSA test stand deployment.    In DM-23437, when doing disaster recovery in InfluxDB, we created a standalone app to deploy InfluxDB called {{influxdb-staging}}. Because that app was not triggered by a parent app, we had to create the namespace, secrets and ingress configuration within the app.    This 'app centric' approach proved to be more interesting and it also makes things look better in the Argo CD UI. Now all Kubernetes objects associated with an app are displayed within the app.    As a consequence, with this reorganization, we also got rid of the special {{ncsa-testand-efd}} parent app."
Answer: 3.0

User story: "Previous attempts to use PSF-matched warps to construct a DCR model failed, but this may have been due to an incorrect PSF size threshold. It should be attempted again with a proper good seeing selection on the input exposures, with the {{ap_pipe}} results compared in a notebook to similar ones using direct warps. If the results are promising, the minor code changes required to enable this option should be made as part of this ticket."
Answer: 92310.0

User story: "Run RC2 bootstrap with Oracle to ensure we know how to do it and it works.     "
Answer: 25781.0

User story: "The definition of which timestamp is used as the InfluxDB time is done in the connector configuration. The default behavior is to use {{sys_time()}}. We want to replace that by {{private_sndStamp}} obtained from the SAL topics.    In DM-21391, we implemented the {{--timestamp}} option in the Kafka connect manager to configure the connector:    https://kafka-connect-manager.lsst.io/cli-reference.html#cmdoption-connect-manager-create-influxdb-sink-timestamp    and in this PR we changed the connector to support to Unix timestamps as double  https://github.com/lensesio/stream-reactor/pull/626    That was released in the version 1.2.3 of the connector:    https://github.com/lensesio/stream-reactor/releases/tag/1.2.3    but, unfortunately, that version introduced a regression and cannot be used (DM-21895).    In this ticket, we'll build a special version of the connector previous to 1.23 that supports Unix timestamps as double.    We'll also need to update the kafka connect manager Helm chart so that we can configure which timestamp to use.    Then, we'll deploy the new connector in the Tucson teststand. For testing the connector with the {{private_sndStamp}} we'll send data to a second database."
Answer: 18855.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "Make QueueModel.next_group_id a static method"
Answer: 179.0

User story: "Update the simulator in ts_hexapod with the correct geometry for the hexapod. That way when the CSC is run in simulation mode the commanded actuator lengths will be at at least approximately correct.    One known reason that the simulator may still differ from the Moog code is that the simulator assumes that pivot rotations are applied in order: x, y, z. For small rotations it doesn't matter much, but for larger motions the order is important.    Also change the simulator so length = 0 at nominal position (with the position set to 0,0,0 0,0,0)."
Answer: 1365.0

User story: "Currently in the IDL Conda packaging process the XML version is hardcoded into the Jenkinsfile.conda recipe.  This is bad, as each XML release requires a ts_idl release.  Figure out the best way to parameterize this value.  Build parameter?  Docker image Env Var (prompting a new image with each XML release)?  Other?"
Answer: 21697.0

User story: The plate scale for LATISS is set to 0.2 arcsec/mm (like the lsstCam), and the boresight is set to the bottom-lefthand-corner of the `RXX` "raft".  Please fix these
Answer: 62.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: Injecting fake point sources is necessary to characterize AP detection efficiencies (and is e.g. required to satisfy DMS-REQ-0097).  We need the capability to inject fake point sources at controllable positions (e.g., relative to known galaxy positions) and fluxes prior to image differencing, and to be able to bookkeep which of the fake sources were detected and with what measured properties.  The injected fakes should be both "transients" (i.e., with no flux in the coadd) and "variables" (with differing fluxes in the coadd and calexp).    This ticket is to sketch a design for implementing this within the AP system.
Answer: 10042.0

User story: "Deploy the LSST-IT puppet stack in NCSA 3003 so nodes can start using it.    Not sure if the current puppet master (pup-ncsa) is already in use or not. If not, will have to deploy a new puppet master as well."
Answer: 8522.0

User story: "with the -Og flag set some integration tests fail because of incorrect column headers in results."
Answer: 1364.0

User story: "lsst-telegraf-0.ncsa.illinois.edu (141.142.181.240) needs to be able to query the kubelet api on a cluster head node over port 6443 for metrics. We can use lsst-nts-kubh01.ncsa.illinois.edu (141.142.238.20) for this.    Allow destination port 6443 from 141.142.181.240 to 141.142.238.20"
Answer: 2684.0

User story: "librabbitmq-c does not have a rpm associated with it. It used to be install via yum repos but the compiled version fixes a tcp keepalive issue."
Answer: 33557.0

User story: "Build and test qserv master nodes  This ticket had been created automatically Primavera ID: None"
Answer: 67692.0

User story: "<USER>(and possibly others) will be working with Dask in the HTCondor DAC cluster to run Data Explorer jobs."
Answer: 242232.0

User story: "Testing the new conda env I had a failure in ci_hsc_gen3 and the failure triggered a failure in the multiprocessing module reporting the failure.  The {{ScalarError}} exception is a subclass of TypeError that takes two parameters. Unfortunately when a {{ScalarError}} is pickled only a single parameter (the message string) is stored and passed to the constructor so reporting the error state fails.    The fix is to make the second parameter optional and to assume that the first parameter is the error message if that's all that is given."
Answer: 467.0

User story: "There's an error in filling out the file_transfer_completed_ack message, where OBSID is expected, but doesn't exist."
Answer: 62.0

User story: "We want several jobs to use the Git Tag name in the job, since the tag contains the application version information.  Currently, the GIT_TAG_NAME variable, provided by the [git-tag-message|https://plugins.jenkins.io/git-tag-message/] plugin, does not work in pipelines.  Therefore, a different implementation is needed until the plugin is updated."
Answer: 3177.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "We will need access groups and service users/groups for the HTCondor DAC and Prod clusters, equivalent to what was set up in LSST-2319 and LSST-2321.    Specific details to come in a ticket comment."
Answer: 3.0

User story: "Update the unit tests in ts_externalscripts and ts_standardscripts for the ts_xml 4.7 compatible version of ts_salobj. group ID must be set before a script can be run.    Note that these changes will not be backwards compatible with ts_xml 4.6 because the group ID is stored in script in the evt_groupId attribute, which only exists for ts_xml 4.7."
Answer: 1609.0

User story: We want to run Scripts with masterPriority=0 in order to make sure that they never become "master", which would trigger an expensive system-wide DDS realignment.    ADLink knows of no programmatic way to do this, but we can easily use env variable substitution in the {{ospl.xml}} configuration file and that variable can be optional. I suggest the following, where {{masterPriority="$\{OSPL_MASTER_PRIORITY:\-1\}"}} sets the master priority to the env variable OSPL_MASTER_PRIORITY, if defined, else 1. Yes the minus sign is needed (I checked that): the default delimiter really is ":-".    {code}  <DurabilityService name="durability">      <Network>          <Alignment>              <TimeAlignment>false</TimeAlignment>              <RequestCombinePeriod>                  <Initial>2.5</Initial>                  <Operational>0.1</Operational>              </RequestCombinePeriod>          </Alignment>          <WaitForAttachment maxWaitCount="100">              <ServiceName>ddsi2</ServiceName>          </WaitForAttachment>      </Network>      <NameSpaces>          <NameSpace name="defaultNamespace">              <Partition>*</Partition>          </NameSpace>          <Policy alignee="Initial"                  aligner="true"                  durability="Durable"                  masterPriority="${OSPL_MASTER_PRIORITY:-1}"                  nameSpace="defaultNamespace"/>      </NameSpaces>  </DurabilityService>  {code}    This will make it trivial for scripts to assign themselves a masterPriority of 0 and we can also easily assign an early CSC, such as a SAL/Kafka producer, a higher masterPriority.
Answer: 107854.0

User story: We need to add a FACILITY header to LATISS data with a fixed value of "Vera C. Rubin Observatory". 
Answer: 32.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: Doing  {noformat}  import lsst.daf.persistence as dafPersist                                                                                butler = dafPersist.Butler('/home/mfl/auxTel_repo/')  butler.get('bias', expId=2020012800123) {noformat}  results in  {noformat}  ~/lsst/obs_base/python/lsst/obs/base/mapping.py in lookup(self, properties, dataId)      504             if len(lookups) != 1:      505                 raise RuntimeError("No unique lookup for %s from %s: %d matches" %  --> 506                                    (columns, dataId, len(lookups)))      507             if columns == set(properties):      508                 # Have everything we need  RuntimeError: No unique lookup for {'detector', 'dayObs'} from DataId(initialdata={'expId': 2020012800123}, tag=set()): 6 matches  {noformat}  but doing   {noformat}  butler.get('bias', dayObs='2020-01-28', seqNum=123)   {noformat}  correctly finds the bias.  As you'd expect, the registry shows a single bias only.
Answer: 687.0

User story: "Fix instances of visit, and also patch up config options for LATISS as necessary.    Also, the defect finding task doesn't write things in a way that are ingestable, so fix that too."
Answer: 3684.0

User story: "To implement data replication from the Summit EFD to LDF (phase 1 of the plan outlined in https://sqr-038.lsst.codes) we need a new instance of the EFD deployed on the LSP cluster.    I am blocked on DM-23419 at the moment. I need the plan reviewed and the cluster ready to start the deployment."
Answer: 60198.0

User story: "At present, RawIngestTask is responsible for adding three different types of dimension records:   - exposure   - visit   - visit_detector_region    We should move the latter two to a separate script that is run after RawIngestTask and (at least at present) only after all associated raws for a visit have been ingested.  That will open the door to (later) being able to define different visit definitions for the same exposure (DM-15536).    This will not on its own allow individual raws to be ingested incrementally - RawIngestTask still needs all raws for an exposure to be present in a single invocation so we can add the exposure dimension record once without needing to see if it already exists in the Registry.  That could be fixed by using Database.sync in a new high-level counterpart to {{Registry.insertDimensionData}} that does perform such a check, but we'll first need to figure out how to handle transactions in ingest - Database.sync is not and probably cannot be part of a larger transaction.    But even that is an easier problem to solve than the corresponding one for visits, because (in addition to the synchronization problem) the visit dimension record needs to contain a region that is currently computed from the regions of all of the detectors that went into it (but could be computed from cameraGeom in the future)."
Answer: 111885.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "Kubernetes cluster join tokens are valid for 24 hours. When new nodes are added to the cluster, a new token needs to be created.    This token is stored in Puppet hiera so the module can automatically add nodes into the cluster."
Answer: 2.0

User story: "Generate the ts_xml 4.6 RPMS for the AT service packages, dm_ATArchiver, dm_csc_base, and dm_config_at.  These are all 1.0.0-rc10.       Also generate a new OODS container, using w_2020_06 of the DM stack and 1.0.0-rc3 of the OODS."
Answer: 2957.0

User story: "As suggested at the DM-SST meeting on 2020-02-10, the lsst.verify.task framework should be evaluated as a possible framework for scientific performance metrics.    This evaluation should implement the PA1 metric in the lsst.verify.task framework and give the same result as validate_drp on the ci_hsc dataset     "
Answer: 191386.0

User story: "[~<USER> [on Slack|https://lsstc.slack.com/archives/C2B6X08LS/p1581437432042000]:  {quote}  Hi, is https://github.com/lsst/ap_pipe/blob/master/doc/lsst.ap.pipe/apdb.rst up to date?  I’m getting 'ApPipeConfig' object has no attribute 'apdb' and make_apdb.py: error: no config field: apdb.db_url  {quote}"
Answer: 3445.0

User story: "Qserv operator will install redis using KubeDB CRD. This might be a first track for prototyping redis DB.    A redis section will be added to Qserv CRD, with the number of redis masters."
Answer: 77997.0

User story: "Use Stack w_2020_06 and run    {{fgcmMakeLut.py /datasets/hsc/repo}}     This will write the look-up-table to a fits file at    {{/datasets/hsc/repo/fgcm-process/fgcmLookUpTable.fits}}    Outputs written to {{/datasets/hsc/repo/config/}} will be erased. "
Answer: 2266.0

User story: "As a step towards consolidation of Kubernetes clusters to address a security finding, mgirate ghslacker from the api.lsst.codes cluster to Roundtable and use this to investigate how best to migrate remaining services."
Answer: 5850.0

User story: "RBAC isn't working properly for Roundtable Argo CD. Users are getting the default read-only role. Investigate and fix."
Answer: 1054.0

User story: "Linking + IOD filtering + DIFI (“did I find it?”) analysis.    "
Answer: 90594.0

User story: "With best seeing criteria."
Answer: 73441.0

User story: "The test code for {{MetricTask}} and its subclasses uses code that has since been generalized in DM-22599. Replace this code with the general purpose tools, add more tests as enabled by the new framework, and remove the test utilities in {{verify}}. These utilities are not used anywhere else, so they can be removed without a deprecation process."
Answer: 74619.0

User story: "Reprocess the three HiTS 2015 fields using ap_pipe with the same good-seeing CompareWarp coadd templates as used for January (DM-23069). Make a summary notebook and verify that nothing significant has changed."
Answer: 26072.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "We worked around a bug in OpenSplice 6.9 by importing including a patched ddsutils.py in ts_salobj. That is no longer necessary with OpenSplice 6.10 and it is time to use the standard module."
Answer: 1460.0

User story: "At one time I believe ts_salobj tests/test_speed.py reported transmitting and receiving several thousand messages per second. With the current version of ts_sal tests/test_speed.py is reporting 600-700 messages/second on my Mac. Try to figure out what changed and improve the speed.    Note that v5.0.0 also runs at the same speed and running older versions requires an older Test IDL file because the ackcmd topic has changed."
Answer: 96739.0

User story: "Take the files that I received from Gregory and get them imported into the database and test out some queries."
Answer: 4374.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "SQR-038 proposes two implementation phases for the LDF EFD. Phase 1 is focused on data replication from the Summit EDF to LDF, and phase 2 is focused on the options for long-term storage."
Answer: 75988.0

User story: "ComCam tests will start soon at the Tucson test stand, we took the opportunity to deploy a new instance of the EFD now managed by Argo CD (see sqr-031.lsst.io)    Before pointing the SAL Kafka producers to the new instance we need to migrate the data from the old EFD to the new one so that we can keep everything in the same database."
Answer: 19.0

User story: We were unable to complete the testing of LVV-T28 (technically, it was granted a "Pass w/Deviation" status) because some of the catalogs necessary for testing are not currently produced by the DRP pipelines. Specifically, catalogs created from and relating to difference imaging and alert production are not available for HSC-RC2. Instead of verifying LVV-178 with a single Jira Test Case, there should be separate Test Cases for each catalog type that is to be tested. Write new Test Cases and link them to LVV-178.
Answer: 279032.0

User story: In testing DM-22817 I discovered that lsst_ci doesn't like Astropy 4 because it seems that Astropy with numpy >=1.17 now preserves units inside numpy functions: (resulting in us applying the unit twice):  {code}  /Users/square/j/ws/stack-os-matrix/osx.clang.py3/lsstsw/stack/DarwinX86/validate_drp/19.0.0-7-g12b746e+17/python/lsst/validate/drp/photerrmodel.py:71: RuntimeWarning: invalid value encountered in sqrt  return np.sqrt(sigmaSq)  Traceback (most recent call last):  File "/Users/square/j/ws/stack-os-matrix/osx.clang.py3/lsstsw/miniconda/envs/lsst-scipipe/lib/python3.7/site-packages/astropy/units/quantity_helper/helpers.py", line 32, in get_converter  scale = from_unit._to(to_unit)  File "/Users/square/j/ws/stack-os-matrix/osx.clang.py3/lsstsw/miniconda/envs/lsst-scipipe/lib/python3.7/site-packages/astropy/units/core.py", line 951, in _to  f"'{self!r}' is not a scaled version of '{other!r}'")  astropy.units.core.UnitConversionError: 'Unit("marcsec")' is not a scaled version of 'Unit("marcsec2")'  {code}    (from https://ci.lsst.codes/blue/organizations/jenkins/stack-os-matrix/detail/stack-os-matrix/31182/tests/ )    This fails for testObsCfhtQuick  and testObsDecamQuick
Answer: 5543.0

User story: "During the DM acceptance test campaign (and, in particular, when testing [LVV-T40|[https://jira.lsstcorp.org/secure/Tests.jspa#/testCase/LVV-T40]]), a number of HSC-RC2 images (i.e., visit/filter/CCD combinations) yield large astrometric residuals when comparing LSST stack positions vs. Gaia DR2. The reason for the large residuals is not clear, so we need to explore whether it is due to deficiencies in DM algorithms, or is simply related to specific images or selection of matched stars. Some preliminary investigation was done in test_LVV-T40_T1240.ipynb, but a more careful examination is needed."
Answer: 276815.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "lsst-telegraf-0.ncsa.illinois.edu (141.142.181.240) needs to be able to query the kubelet api on a cluster head node over port 6443 for metrics. We can use lsst-nts-kubh01.ncsa.illinois.edu (141.142.238.20) for this.    Allow destination port 6443 from 141.142.181.240 to 141.142.238.20"
Answer: 205577.0

User story: "Following recent events, there has been a desire to have a simulator for the Hexapod's built by Moog. However, the simulators have not been tested nor documented by us or Moog. I attempted to build the simulator and after many hours was able to successfully build it. "
Answer: 51.0

User story: "h1. Configure database backups"
Answer: 185521.0

User story: "h1. Configure database backups"
Answer: 185522.0

User story: "h1. Configure database backups"
Answer: 185524.0

User story: "h1. Configure database backups"
Answer: 185524.0

User story: "h1. Configure database backups"
Answer: 185526.0

User story: "h1. Configure database backups"
Answer: 185528.0

User story: "Reingest the official repo using the scripts from DM-23361 using obs_lsst from d_2020_02_07 or later.  Move the new repo into the place of the old one, keeping the old one for some time just in case.  Make sure that the new version of obs_lsst continues to be used for automatic ingestion thereafter.    This needs to be done before new images arrive, but it should not be blocking current analysis work that can proceed with unofficial repos."
Answer: 4468.0

User story: "Install an OODS based on d_2020_02_07 or later at the Summit and reingest Summit data (either using copied raw data or the scripts from this ticket or try both).  Move the new repo into the place of the old one, preserving the old one for a few days/weeks just in case."
Answer: 4438.0

User story: "MultiProFit needs a background component to test fitting with a free background level."
Answer: 158287.0

User story: "What will be done:    - [~<USER> will contact Matt Long @NCSA in order to get information on how to set up a k8s cluster for Qserv.  - [~<USER> has written a very simple blog page on how to install k8s with kubeadm: https://k8s-school.fr/resources/en/blog/kubeadm/, this might help Bastien  - [~<USER> has a script to automate k8s install with kubeadm: https://github.com/k8s-school/k8s-advanced/tree/master/0_kubeadm, it works currently on ubuntu and has been intensively tested. If [~<USER> is interested, Fabrice can move it to a given Centos version and document it.  - [~<USER> recommend installing this k8s cluster with containerd and canal (Fix: NetworkPolicy support might be implement in recent weave version, Fabrice should test that before recommanding canal)  - k8s cluster can be mono-master in the short term, multi master will be implemented in an other ticket  - Kubernetes nodes do not require access to GPFS for dataloading (even if NCSA implemented this solution)"
Answer: 114967.0

User story: "The function is hard to read as is and could use some refactoring. "
Answer: 116410.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: This ticket is for running jointcal for HSC-PDR2  WIDE tracts/visits.      To generate the scripts, do the following or equivalent:   {code:java}  git clone https://github.com/lsst-dm/s20-hsc-pdr2-reprocessing.git  cd s20-hsc-pdr2-reprocessing/03_jointcal   ./makeJointcal.sh  {code}    A folder named "WIDE-scripts" should be created, with 3411 WIDE-jointcal-*.sl slurm submission files, and one file named "WIDE-jointcal-submit.sh" that includes 3411 sbatch commands.  You are welcome to take a look at these scripts to understand them though you don't have to.  You may use  "WIDE-jointcal-submit.sh"  to submit jobs directly or split them into smaller batches, similar to DM-23301.   Please run them, keep track of them, check if any fails, and if any fails due to infrastructure reasons please rerun the failed ones.    {{source 03_env.sh}}  before submitting jobs.     Please keep a list of the slurm job IDs of all successful jobs; there should be 3411 items.   These jobs write the log files to {{/datasets/hsc/repo/rerun/DM-23243/logs/jointcal/WIDE/}}  Please delete or move away logs of the failed jobs; there will be 3411 log files in the end .     Some of them will have errors  {{ERROR: Potentially bad fit: High chi-squared/ndof}}.   Please keep a list of those, but then they can be regarded as successful jobs.       This ticket has to wait for the sfm outputs from DM-23301.
Answer: 16717.0

User story: "FGCM with all of the PDR2 data, including WIDE+DEEP+UDEEP.      Input data products: calexp and src. Nothing else.     Cookbook for reference: https://github.com/lsst/fgcmcal/blob/master/cookbook/README.md "
Answer: 27203.0

User story: "I found out that executing {{loadLSST.bash}} twice causes the wrong miniconda bin path to be exposed to the shell.  This is because [here|https://github.com/lsst/lsst/blob/master/scripts/newinstall.sh#L922] the base miniconda bin directory is prepended to the {{PATH}}, however if the virtualenv has already been activated, it does not activate again and the miniconda bin shadows the virtualenv bin path and this means different modules are available than expected.    I'm pretty sure that line can simply be removed since the {{source activate}} should set the correct path in any case.  If it cannot be removed, it should be an append so that sourcing the file multiple times does not end up in a confusing state.    FWIW, I think this is also a problem for the other shell specific files, but have not checked for sure."
Answer: 1519.0

User story: "Update Puppet and xCAT management of Yum to allow pinning of kernel/kernel-related packages (or other arbitrary packages) to specific versions. The main use case is to update other packages while keeping the kernel to a specific version to maintain GPFS compatibility. As usual, we need the ability to rebuild nodes and patch nodes to the identical configuration."
Answer: 206870.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "Task 1: We currently add and manage the EPEL software repo config on all of our clients (originally required by Nagios; also installed by xCAT to ensure it was there from the beginning; once Nagios was phased out we added in extra::yum). Do we need it everywhere? If not, can we only require it on nodes that need it?    Task 2: For Puppet management, do we need to use the 3rd-party 'epel' module or can we convert to a simple 'yumrepo' Puppet resource? Note that if we use other 3rd-party modules that require the 'epel' module we'll probably have to stick with that route."
Answer: 206600.0

User story: "Using lsst-it/docker_puppet, on a Vagrant VM, vagrant user cannot sudo after running puppet."
Answer: 1.0

User story: "This option was deprecated in release 19.0.0; it should be removed before 20.0.0."
Answer: 106567.0

User story: "Get the NCSA branches merged into LSST-IT master for control and hiera repos.    Travis tests running against the PR are failing, some look like false positives. Work with LSST-IT folks to updates tests so PR can continue.    Also coordinate with LSST-IT folks to test the branch on a node at their location (Tucson and/or Base Data Center) to verify it doesn't break anything."
Answer: 17101.0

User story: "puppet-ssh (used by NCSA) conflicts with saz/ssh (used by LSST-IT).    Revamp puppet-ssh to work alongside saz/ssh.    LSST-IT won't use puppet-ssh and NCSA won't use saz/ssh, but both modules will be installed at the same time so can't have any duplicate class names."
Answer: 1.0

User story: "This method has been marked as deprecated since release 11, and its deprecation was announced with release 19.0.0. Remove it."
Answer: 89525.0

User story: "{{lsst.ip.isr.addDistortionModel}} was announced as deprecated in release 19.0.0 on DM-20154. Remove it before release 20.0.0."
Answer: 119554.0

User story: "Should include a note on what is deprecated in this release; we can then keep the notes updated until the release actually happens."
Answer: 193.0

User story: "[~<USER> reports that old LATISS data has no OBSID or DAYOBS headers so ingest fails.    The fix is to add them from the IMGNAME header during header fixup phase.    see eg /lsstdata/offline/teststand/auxTel/L1Archiver/storage/2019-03-06/AT_O_20190306_000014-ats-wfs_ccd.fits"
Answer: 1588.0

User story: "Not having {{expId}} in the registry is blocking work and making this very painful. Ideally this would be done with DM-23281 merged, but given that it should be a ~single button press, and that it will need to be done more than once, practicing now should be a priority I think.    If people are unhappy about losing the old repo at this stage, I suggest moving the old one rather than deleting it.    This ticket is now about determining and writing any scripts needed to accomplish this but not actually performing the reingestion, which has been moved to additional tickets."
Answer: 2059.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "[~<USER> notes that {{\_\_file\_\_}} is not supported by config files in pex_config. Looking at the code it seems trivial to add support for this."
Answer: 2368.0

User story: "Create a template for github.com/lsst/templates that helps us create aiohttp-based bots for Roundtable (https://roundtable.lsst.io).    This template will leverage the Safir framework (DM-23355)."
Answer: 30316.0

User story: Create a framework to make it easier to build apps for Roundtable / SQuaRE Events / sqrbot(-jr). This framework will take care of a lot of patterns that need to be commonly performed. The functionality will be drawn from existing apps:    - https://github.com/lsst-sqre/sqrbot-jr  - https://github.com/lsst-sqre/templatebot  - https://github.com/lsst-sqre/lsst-templatebot-aide    The framework will be designed so that multiple web frameworks can eventually be accommodated, though the framework will be developed for {{aiohttp}} first.    The suggested name is "safir" - a knight of the round table and also evocative of "SQuaRE framework"
Answer: 30156.0

User story: "Task to cover time taking the LinkedIn Learning Jenkins Essentials course.    https://www.linkedin.com/learning/jenkins-essential-training/next-steps?u=37426900"
Answer: 72.0

User story: "{{forcedPhotCcd}} needs to be able to apply the jointcal/fgcm and skyCorr recalibrations. Because this matches logic elsewhere in the pipeline ({{MakeCoaddTempExpTask}}), this will involve some refactoring, and because it involves I/O, we need to keep Gen3 happy."
Answer: 9871.0

User story: "Around a week after DM-22817 updates the conda env, update the eups third party stub package version checks to match the new versions."
Answer: 144192.0

User story: "Once the conda env is updated in DM-22817, a new shared stack needs to be created."
Answer: 23436.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "||Task||Relevant Information||Notes||  ||Information Gathering|| || ||  |list of Hostname(s) and IP(s)|lsst-qserv-master03 (141.142.181.162)   lsst-qserv-master04 (141.142.181.163)| |  |list of Administrators   At least one FTE included in list|lsst_sysadm (NCSA admin)       Non NCSA access:|    lsst_int_qserv_devs (sudo)|    lsst_int_qserv_devs (sudo)   lsst_int_kubernetes (ssh access, but no sudo)| |  |Group that owns the system| LSST| |  |Machine general use and purpose| Qserv Master / Cassandra APDB testing (along with qserv-master02)| |  |Operating System|CentOS Linux release 7.7.1908 (Core)| |  |Compile list of remote services| sshd   Possible database stuff (?)| |  ||Access for NCSA Security|| || ||  |Configure access for the security   team and root escalation| from cerberus, ssh to lsst-adm01, escalate to root, ssh to qserv-master0[3-4]       Can also ssh from cerberus -> lsst-bastion01 -> sudo su - from node itself.| |  |Configure access for Qualys Scans|[https://wiki.ncsa.illinois.edu/x/e6V4Ag]| |  ||Access Control|| || ||  |Remote root login has been disabled| In sshd config:   PermitRootLogin no    Root login without password is allowed from several nodes. Primarily qserv nodes. This might be able to be negotiated down while Cassandra testing is active.| |  |Removed unnecessary local accounts| Yes. Standard xcat/puppet deployment| |  |Accounts checked for use of SSH keys| | |  ||Authentication and Authorization|| || ||  |System uses Kerberos & LDAP for auth/authz| Yes| |  |Sudo has been configured for root escanaltion| Yes| |  ||Kerberos|| || ||  |Check /root/.k5login configuration|   file does not exist| |  |k5login report script has been installed| n/a| N/A|  ||Two-Factor Authentication (2FA)|| || ||  |Root escalation path requires 2FA| ssh is only possible from hosts behind 2FA| |  |Host uses a 2FA bastion for admin access|Yes. See above. | |  ||System Services|| || ||  |Unnecessary services have been removed or disabled| Yes, excluding packages with active open tickets.| |  ||Host-Based Firewall|| || ||  |Host-Based firewall has been implemented|[https://wiki.ncsa.illinois.edu/x/HZ54Ag]| iptables|  |Other controls have been implemented (tcpwrappers)| pfsense, pam access, sshd config| |  ||SSH - Secure Shell|| || ||  |SSH Service has been configured|[https://wiki.ncsa.illinois.edu/x/FQx4Aw]|     |  ||Remote Logging|| || ||  |System is configured to forward logs to central syslog|[https://wiki.ncsa.illinois.edu/x/QyPJAQ]| |  ||Time Synchronization|| || ||  |System is configured to sync time via NTP|[https://wiki.ncsa.illinois.edu/x/wgC9Aw]|  chronyd|  ||Filesystem|| || ||  |This system uses GPFS| Yes| |"
Answer: 37373.0

User story: "In addition to the new masters, we also got 6 new qserv worker nodes. They are to be added to the k8s-prod cluster and network."
Answer: 77950.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "I am going to create a new cluster definition in hiera for qserv-master0[2-4] since these nodes do not need all of the same data as the regular qserv nodes.    Aside from the new cluster, there doesn't seem to be a reason why the Cassandra test nodes shouldn't be given the qserv role/profile."
Answer: 278.0

User story: "The new kub nodes have been racked but need to be added to their respective clusters."
Answer: 138404.0

User story: "Implement RFC-661."
Answer: 349778.0

User story: "Following RFC-661, ensure that Synpipe is marked as deprecated before the next major release (20.0.0)."
Answer: 138443.0

User story: "DM-23213 broke {{ingestDriver.py}} by changing the API of {{IngestTask.runFile}}."
Answer: 1225.0

User story: "{{Install 2x 40GbE cards for DTN nodes. }}"
Answer: 60597.0

User story: "Find appropriate MLX 40GbE cards for DTN nodes for Rucio+globus.    1. Find the correct model   2. Place order with Kaylyn"
Answer: 60599.0

User story: This should be considered an end-user request and not a security required change. As a future user of the new LSST login nodes, I would like to have GSSAPIStoreCredentialsOnRekey yes set in sshd_config. This settings controls "cascading credentials" which allows Kerberos tickets on my client to be pushed to the remote machine when my SSH client re-keys the active session. This avoids the need to periodically manually kinit on the remote host as tickets will be automatically refreshed as long as the SSH session is active. Since we are allowing Kerberos ticket forwarding (with Duo) it makes sense to also allow periodic ticket renewal.
Answer: 69462.0

User story: "We should review our overall sshd_config settings on the new login nodes (any first hop nodes) and probably any new dev/interactive nodes.    See for instance:   https://jira.lsstcorp.org/browse/IHS-2816   Users seem to expect that their inactive SSH sessions will stay active for 24 hrs+."
Answer: 69465.0

User story: "Security vetting of Yum repo server for NCSA 3003"
Answer: 208548.0

User story: "Security vetting of Yum repo server for NCSA 3003"
Answer: 8.0

User story: "Update the packaging of https://github.com/lsst-sqre/ltd-conveyor to use a pyproject.toml and setup.cfg file. This will be in preparation for releasing ltd-conveyor 0.5 to PyPI."
Answer: 958.0

User story: "Document known security gaps in SQuaRE services and practices so far as currently known, in a framework that can be updated in the future as more are discovered and gaps are remedied or mitigated."
Answer: 4240.0

User story: "Now that {{fgcmcal}} is ready for full production, a set of recommended default config files can be added to {{obs_subaru}}, including look-up-table building, chromatic correction information, mirror coating dates, etc."
Answer: 4218.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "This testing is to be done with our Puppet CRON scripts for OS updates. We need to test on both CentOS 6 & 7 servers, and also be sure to include some GPFS clients.    This would most likely happen on at least the following hosts:   * lsst-dts   * lsst-test1   * lsst-test4   * lsst-test5   * lsst-test6   * lsst-test7   * lsst-test8"
Answer: 24637.0

User story: "Test Dell firmware patching on some sample Dell hardware in NCSA 3003:   * Dell R640   * Dell C6420   * Dell R730    This would be applied using Dell maintenance CRON scripts from Puppet that run Dell's {{dsu}} command."
Answer: 2941.0

User story: "We need to apply rolling updates to our VMware ESXi nodes on a regular basis. I suggest we do this during the same week as our quarterly major PMs (but avoid any updates during the actual PM time). These updates should be transparent to the VMs that run on the servers, as those VMs can manually be live migrated around during the rolling update process.    The updates should include:   * ESXi patching and upgrades   * Dell Firmware upgrades (in particular BIOS, iDRAC, & NIC drivers)   * Optionally datastore VMFS upgrades"
Answer: 100692.0

User story: "Use Furusawa-san’s list, ignore new data that we don't have, run jointcal for DEEP & UDEEP (together) "
Answer: 18721.0

User story: "We have three PDAC machines (almost) ready for use in APDB test with Cassandra, these are lsst-qserv-master0[2-4]. I need to install and configure Cassandra cluster on those three nodes in some initial configuration, subject for optimizations later. master02 is older machine with smaller SSD storage, other two machines are new hosts with larger storage."
Answer: 4708.0

User story: "In DM-23496 we need to deploy a second {{influxdb-sink}} with a different configuration. That is not currently supported by the {{kafka-connect-manager}} because the name of the connector is fixed.    https://docs.confluent.io/current/connect/references/restapi.html#post--connectors    Adding a {{--name}} option to  {{connect_manager create influxdb-sink}} command is totally reasonable and will make it more generic. "
Answer: 20312.0

User story: "The dominant failure mode in `meas_extensions_scarlet` is a parentheses that is outside, rather than inside a set of parentheses. Correcting this should fix the large number of errors that we are seeing when using 2-component models and bring the failure rate down to the same rate as the other deblending methods at a small fraction of a percent."
Answer: 4860.0

User story: "Following   [the obs_lsst change |https://community.lsst.org/t/change-to-visit-definition-for-lsstcam-and-latiss/4014] we need to re-ingest the  /datasets/DC2/repoRun2.2i  repo "
Answer: 2513.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "With DM-23069 complete, we will have a good new set of HiTS2014 templates made with the best seeing selector requiring a maximum PSF FWHM of 1.4 arcseconds. This ticket is to update ap_verify_hits2015, ap_verify_ci_hits2015, and any other dataset I am forgetting to use these new templates and remove the old ones."
Answer: 172812.0

User story: "Add Urgent field to DM project to see if it can be used to indicate critical faults affecting the use of telescope time.    Note: this ticket filed to test the work"
Answer: 10033.0

User story: "To use the  {{local-path-provisioner}} in DM-23064 we are exporting NFS with {{no_root_squash}}.    It seems we can avoid that by using the {{securityContext spec}} in the pod, see for example:    https://github.com/rancher/local-path-provisioner/blob/master/examples/pod-with-security-context.yaml"
Answer: 352774.0

User story: "h4. Description   * Merge data from pup_hiera into lsst-puppet-hiera   * Merge modules from pup_control into itconf (control repo)   * Test in docker_puppet   * Test on physical host in ncsa test stand"
Answer: 35949.0

User story: "Update the MTM1M3 XML to be compatible with running m1m3 support code, then update the code to use the new naming"
Answer: 38542.0

User story: "singleFramDriver using w_2020_05     Commands are in 01_sfm_deep.sh and 01_sfm_Udeep.sh at   [https://github.com/lsst-dm/s20-hsc-pdr2-reprocessing/tree/2df940f033ce786739ec2f8e0c682aaed7fca1e3/01_sfm]"
Answer: 5947.0